You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I've longed to plot dynamically the output of a high resolution irtt sample, but the output has two problems in that it uses mixed units (us, ms, s), and the one way delay measurements require a sync'd clock. the rtt measurement does not. (ok, that's three problems).
The json output doesn't use mixed units but requires the test complete before plotting. four problems. A command line option to always use ns would help.
a typical test I do is:
irtt client -i3ms -d1m --dscp=0xfe
and then I parse that with tr, awk and gnuplot. There isn't a way to send the json output (-o whatever.json) to a stream either. I have some really cool plots of how starlink works but haven't twiddled it enough to do one way delay yet (five problems).
The text was updated successfully, but these errors were encountered:
The during-test output was intended for humans, and the json for programs. The data is collected first in memory then dumped in one big chunk. That would have to be re-worked, but it's possible.
from this thread over here:
https://forum.openwrt.org/t/validating-nss-fq-codels-correctness/111123/33
I've longed to plot dynamically the output of a high resolution irtt sample, but the output has two problems in that it uses mixed units (us, ms, s), and the one way delay measurements require a sync'd clock. the rtt measurement does not. (ok, that's three problems).
The json output doesn't use mixed units but requires the test complete before plotting. four problems. A command line option to always use ns would help.
a typical test I do is:
irtt client -i3ms -d1m --dscp=0xfe
and then I parse that with tr, awk and gnuplot. There isn't a way to send the json output (-o whatever.json) to a stream either. I have some really cool plots of how starlink works but haven't twiddled it enough to do one way delay yet (five problems).
The text was updated successfully, but these errors were encountered: