On Mon, 8 Feb 2021 at 14:03, mick mbm@rlogin.net wrote:
As Jonathan's reply suggests, you should probably be looking at latency problems. But smokeping drags in a lot of other dependencies (including apache) which you may not want.
I think latency might be the issue, but my problem is that most tools* like to give you a nice average rather than looking beyond that. A standard speed test would be helpful if as well as the average throughput it gave me min/max kbps figures but that seems so simple that there must be a reason why they don't. I tend to use speedtest-cli which is just a Python script so I might look into what it is actually doing.
* Most end user tools, anyway
Try the simple approach first and use ping, traceroute etc to see if there are any obvious slow spots in the network paths. A good alternative to straight ping is "oping" and its ncurses front end "noping". noping highlights any rtts it deems "aberrant".
noping is reporting times varying from 11ms to 43ms when run directly on the (OpenWRT on a Pi4) router. --- 8.8.8.8 ping statistics --- 133 packets transmitted, 133 received, 0.00% packet loss, time 2033.1ms RTT[ms]: min = 11, median = 14, p(95) = 23, max = 43
Is that good/bad?
If you are interestred in the latency of traffic to/from a webserver then try httping (which also has a nice ncurses front end.
--- http://www.google.com/ ping statistics --- 45 connects, 45 ok, 0.00% failed, time 46958ms round-trip min/avg/max = 37.8/49.5/65.8 ms
Again, with nothing to compare to I don't know how good/bad that is.
Thanks for the suggestions, I now feel I have more information and no more idea what the problem is :-)