Here’s another real world example of troubleshooting performance problems. An email subscriber, Simon, contacted me about poor Tomcat throughput on Windows 2008R2 – whenever Tomcat served a large file, download speed sucked. To Simon’s credit, he eliminated “the network” by verifying that Apache and IIS did not have the same issue.
Here’s where a mediocre network engineer or admin might say “sorry, not my problem” and push it back to the application guys or server guys. Not Simon. Simon understands that no one cares if your network is fast, efficient, and well designed. People care about applications and when applications perform poorly over the network, people yell and someone has to solve it. I love it when people step up and own a problem that’s not technically theirs. That’s what top performers do.
Further to Simon’s credit, he diagnosed the issue and came up with a solution. He asked me my thoughts and if there was another possible solution.
My Wireshark code changes for Segments ACKed. As of Wireshark 2.2 the “bytes since last PSH bit” is included as
A PacketBomb viewer wrote a Wireshark Lua script to do the same thing