One way to identify network-limited performance problems is by getting your JVM to dump out stack traces while your system is under load. You can tell if your system is network limited because your thread dump will show lots of threads waiting in socket reads or writes.
One sign of network-limited performance problems that may show up in a Java VM dump is threads waiting to read from the Connection Module called from the sendReply method. In this case, the DRP Server has written the data to the Connection Module. The Connection Module is in the process of writing the data to the client. When the Connection Module has finished, it sends an acknowledgement to the DRP Server that it has finished. This is likely to happen when sending a large file to a client with a slow network connection.
Some ways to address network-limited problems include:
Reduce the size of your HTML files by limiting comments and white space or redesigning the content of especially large pages.
Increase the number of request handling threads. This won’t improve the latency experienced by a user who requests a large file, but it will improve total throughput.
Get a faster network connection.
Locate and correct network bottlenecks.
