Hi all, please consider participating in the poll below to help me gauge interest in which iperf3 locations should be used by YABS for network testing. There are 18 options, but please narrow down your selection to your TOP 5 choices.
If there’s any reason you DON’T want a specific location added, please voice your concerns here (i.e. if you’ve experienced reliability issues, location is significantly slower than others in the same region, etc.). I appreciate all the help! Feel free to share the poll link with anyone else that regularly uses the script. @Clouvider has recently added public iperf3 servers to all 6 of his POPs, so there’s plenty of “new” locations to consider.
In other news…
YABS updates in the works:
Fix web scrape to get GB4 results from curl (GB’s web design changed slightly, so it doesn’t grab the scores currently) – DONE (implemented in ‘testing’ branch)
Add longer wait time after GB test concludes to allow results to be posted in time – DONE (implemented in ‘testing’ branch)
Add ability to use a GB paid license key to unlock the full GB test – DONE (implemented in ‘testing’ branch)
Update pre-compiled binary for fio (v3.17 → v3.23)
Update pre-compiled binary for iperf3 (v3.7 → v3.9)
Alter iperf3 test locations for the network speed tests based on feedback provided in the poll
Holy cat @Clouvider is the main sponsor! But would definitely love to see Zurich, to be honest. So I would have a lot of fun testing our few nodes at 10gb/s.
Since there are more options on Western Europe and US, may I suggest we keep the more “exotic” locations: Bogor, Sao Paulo, Kiev and Moscow independently of the poll results?
Thoughts on this batch of iperf tests? Interested in what you think about the location choices. Trying to find the right balance of geo-diversity and popular datahubs.
Really just depends on the iperf servers that are publicly available. APAC doesn’t have any available as far as I’m aware besides the Biznet location. I’ll be on the lookout for more, though
Ahh yeah… I don’t think the fio, iperf, or geekbench binaries will work with arm. Maybe it’s worth exploring making it arm-compatible if I can compile fio and iperf for arm.
I’ll look into it, but I’m not really a BSD guy so no idea what would be involved. But the project is open source for a reason!
Works fine on zfs-backed systems (…if your machine can handle it lol). Fio, iperf, geekbench will naturally try and max out the resource it’s testing and doesn’t really care what else your machine is running. The disk calculation hasn’t been worked out yet since df reports strange values for zfs systems (hence why other bench scripts report more storage space than you actually have).
fio and iperf/3 are available on arm sir.
I guess you could at least add a update so it runs without geekbench until you made or not made that working. Nearly everything is available on arm64 but not on armhf which 32bit RPi4’s use.
Hm, getting this on a couple of nodes (both NAT nodes and IPv4 public nodes): Geekbench releases can only be downloaded over IPv4. FTP the Geekbench files and run manually.
On nodes which have both IPv4 and IPv6 … Anything I should check on my end?
(I guess @Mason would be the one to ask here.)
Means the IPv4 check is failing for some reason. It’s done via a curl to icanhazip.com. Maybe I need to re-evaluate how it determines IPv4 connectivity and switch it to using ping or something like that instead. Unless someone has any better ideas?