4 ms·
Out of curiosity, how would you debug this issue with Wireshark? Just look for multiple messages in a single TCP packet? Or is there a better way?
by LeonM 6y ago
Out of curiosity, how would you debug this issue with Wireshark?
Just look for multiple messages in a single TCP packet? Or is there a better way?
- deleted 6y ago[deleted]
- pwinnski 6y agoRight? If seeing multiple messages in a single TCP packet immediately clues you in to the issue, the truth is that you already knew about the issue.
- marcosdumay 6y agoNo kidding. I imagined Google or DDG would turn "multiple messages in a single TCP package" into something useful, since it's basically the description of the algorithm. But no luck. The best I got was somebody with an IO buffering problem in Stack Overflow that commented that he turned the algorithm off.
- bostik 6y agoIf you're debugging weird latency problems, I'd recommend to start from relative timestamps. Then filter to just one or two TCP streams that exhibit the problem and go from there. Inspect packet contents. The packet dissectors are doing a lot of heavy lifting, so look at the deconstructed data. I realise this may not be a welcome suggestion, but a sharp pencil, an A3 (or larger) scratch pad and a good ruler go a long way. I've dug to the bottom of quite a few network and traffic problems in my life by drawing the observed traffic patterns into sequence diagrams. Once you have the diagram visualised, it's easier to spot the places where something funky either happens or looks to be missing.
- PeterisP 6y agoWell, as soon as you'd look for and find any one of your messages in wireshark to use as an example, then you'd notice that the packet has not only that message but others as well.