Graphs and tools for showing "bufferbloat"
Description
Hi. I would love wireshark to get more tools to show what normal tcp sawtooths should look like, and to be able to show "bufferbloat" where it happens.
Over the years in the "flent" tool primarily, we've developed tons of means of generating traffic and plotting it, and we also use ancient tools like xplot.org to show it. We've mostly used this to show the benefits of fq-ing and aqm algorithms.
The thing is, we use these tools, rather than wireshark directly, because no-one on the team(s) has any lua experience, and comparing the effects of two or more flows against each other directly within it, seems hard. Secondly, we also tend to generate it with active measurements, rather than the sort of passive measurements against real traffic wireshark is often used for. A "bufferbloat detector", showing a tcp latency inflation of greater than X (say, 30ms), would be a nice warning to have (kind of like how wireshark detects a retransmit), the ability to plot more than one flow against each other at the same time, another.
Other graphical ideas and detection mechanisms would be welcomed. (as well as advice as to how to better use wireshark filters or tools in our work)
Similarly, being more able to detect when an aqm like pie or codel is on the link (vs tail drop) would be great, similarly the presence of fair queuing.
I realize these are wide open questions, but not knowing what can be done in wireshark is part of the question.
Links / references / protocol specifications
If you google for bufferbloat or fq_codel you will find all kinds of graphs, notably of flent's rrul test. See also:
https://www.ookla.com/articles/introducing-loaded-latency
https://forum.openwrt.org/t/aql-and-the-ath10k-is-lovely/59002/