What would be interesting is having a distribution of the peaks for
fusion/latency. I wonder if this is a one shot problem at startup, or a
continuous jitter spreaded all over the test.
# at startup:
min = 5073 ns, max = 17235 ns, avg = 5930 ns, overrun = 0
min = 5073 ns, max = 19038 ns, avg = 5989 ns, overrun = 0
min = 5073 ns, max = 19038 ns, avg = 6062 ns, overrun = 0
min = 5073 ns, max = 19038 ns, avg = 6057 ns, overrun = 0
# while typing this email:
min = 5073 ns, max = 29922 ns, avg = 6042 ns, overrun = 0
min = 5073 ns, max = 29922 ns, avg = 6015 ns, overrun = 0
min = 5073 ns, max = 29922 ns, avg = 5963 ns, overrun = 0
min = 5073 ns, max = 29922 ns, avg = 6016 ns, overrun = 0
min = 5073 ns, max = 29922 ns, avg = 6126 ns, overrun = 0
# with ping -f
# and while true; do echo `seq 1 46`; done
min = 5073 ns, max = 32894 ns, avg = 8447 ns, overrun = 0
min = 5073 ns, max = 45732 ns, avg = 8667 ns, overrun = 0
min = 5073 ns, max = 45732 ns, avg = 8419 ns, overrun = 0
min = 5073 ns, max = 45732 ns, avg = 8386 ns, overrun = 0
min = 5073 ns, max = 45732 ns, avg = 8389 ns, overrun = 0
# dd
min = 5073 ns, max = 45732 ns, avg = 8897 ns, overrun = 0
min = 5073 ns, max = 55220 ns, avg = 9098 ns, overrun = 0
min = 5073 ns, max = 55220 ns, avg = 9374 ns, overrun = 0
min = 5073 ns, max = 67279 ns, avg = 9068 ns, overrun = 0
min = 5073 ns, max = 67279 ns, avg = 8722 ns, overrun = 0
min = 5073 ns, max = 67279 ns, avg = 8447 ns, overrun = 0
....
min = 5073 ns, max = 67279 ns, avg = 8751 ns, overrun = 0
min = 5073 ns, max = 72061 ns, avg = 10184 ns, overrun = 0
min = 5073 ns, max = 72061 ns, avg = 10651 ns, overrun = 0
