public-iperf3-servers VS goresponsiveness

Many hosting/VPS providers run iperf3 servers you can hit, which can be useful.

Why, here’s some now!

https://github.com/R0GGER/public-iperf3-servers

If you decide to play around with iperf3 you can find a list of public servers here: https://github.com/R0GGER/public-iperf3-servers

Ich würde ein iperf3 gegen verschiedene Ziele (z.B. Wilhelmtel, Severius.. https://github.com/R0GGER/public-iperf3-servers) machen.

On https://github.com/R0GGER/public-iperf3-servers you can choose a iperf3 server closer to you ... see if you get a higher speed.

> which is more reflective of real world video conferencing use cases

What's more reflective of real world use cases is a hot discussion topic. :)

The networkQuality tool on macOS and other implementations(1) of the "RPM" algorithm(2) are very good to see how an Internet connection behaves under high stress. But the real world is seldom high stress (100Mbps+ connections are rarely pushed to the limit, honestly).

In your example, video conferencing indeed does simulataneous upload and download, but it's also low bandwidth (relatively speaking) and doesn't usually come close to saturating a connection. It can impacted by other traffic in the same connection though.

Neither networkQuality nor Cloudflare's speed test measure how a connection behaves with multiple users stressing a connection, which is another example of why this is a hot topic.

(1) https://github.com/network-quality/goresponsiveness

Apple's "networkQuality" tool (or the open source alternative that you can run in other operating systems: https://github.com/network-quality/goresponsiveness) is very useful to understand how your connection behaves under extreme conditions, but extreme conditions is not something a home connections sees regularly, so make sure to use a combination of tools if you want to understand your home connection behaves under expected use.

It's more of an art than a science, really, and your ISP may be optimizing for more average use cases.

Personally I like to start with a regular web-based speed test (I'm biased towards https://speed.cloudflare.com, but any test that shows latency under load is OK, like https://www.waveform.com/tools/bufferbloat or https://fast.com[1]) and then combine it with "networkQuality" running concurrently (if possible, from a different host) and see how it impacts the numbers.

Of course, this only makes sense if you, for example, have your own router running OpenWRT where you can enable active queue management (SQM/AQM) where you can actually do something to improve the results.

[1] In more recent times I'm finding fast.com to be a bit unreliable, as some ISPs may treat Netflix traffic specially (like allowing for longer bursts over contracted speeds, etc. — net neutrality notwithstanding).