OpenSpeedTest

OpenSpeedTest is basically a speed test in your web browser you can run locally. It is used most commonly to verify the practical throughput from one host to another. Though, it is far from perfect, and you cannot use it for any host or service. For that it is better to use iperf3. But it works for any device having a web browser.

While using it I found two issues that made the result quite interesting and one weary on both client and server configs. For the server, they specifically say that if used with a reverse proxy one needs to make sure that the post body size is larger than 30MB, or more specifically 35MB. Some additional changes are disabling logs and gzip, and avoiding https. One would assume more cores and RAM could be beneficial, but as the project is static files and client script, it isn’t actually an issue at all.

For the client side, all it matters is the amount of RAM and CPU power. For CPU, I do not really get why, but somehow it requires more cores too, I would assume it has something to do with JavaScript just requires loads of processing of that data. For RAM, I only found out that it is due to the redrawing of the webui, which is really silly.

Overall, I found out that Windows has a rather bad performance with this, but Linux could reach at least 2Gbps on the server, which is neat. It is a small project, but it sure provides all features needed to profile your network, even continuous load.