wmertens

See those are super interesting 😊
 
At some point it would probably also be nice to use stacked bars as the histogram bars so you can e.g. also group by age.

Sorry it's taken me a couple of days, I'm developing.
 
If you toggle the beta in My Settings, then visit the upload or download test there's an explanation.
 

 
There are reasons I originally did it that way and they still hold true.  It makes for a more consistent test with far less variables.
 
Man!  Your suggestion for the upload test back in 2018.  That's an algorithm I still use.  Has saved a lot of bandwidth and time... no joke, over the hundreds of millions of upload tests since, probably something like a decade or more of wait time saved at this point.  I can calculate the bandwidth saved... I'll just estimate quickly, going off the recent upload test results
 
Keep in mind, what's logged to the database is the final result.  The client may have cycled though up to 4 tests before getting to the final test.
 
2 GB in the last 4 minutes (non-peak early morning hours)
 
1440min per day / 4minutes = 360 * 2GB = 720GB per day
 
The optimization was made 6 years ago
 
720*365*6 = 1,576,800 GB or 1.6 Petabytes!
 
Wow.  I think you could easily figure an extra 30+% for the pre-tests.  So about 2 PB saved!
 
Using the current median download speed from the recent download test results of 62 Mbps we can get a rough estimate of the time saved.
 
byte conversion
62/8 = 7.75 MB/s
 
2 PB is 2147483648 MB
(2*1024*1024*1024)
 
2147483648 / 7.75 = 277094664 seconds saved
 
(((277094664 / 60sec per min) / 60min per hr) / 24hrs per day) / 365days per yr = 8.8 YEARS SAVED!
 
The actual number is probably much higher.  Your post, I'd say has saved at least 10 years of wait time collectively.  Amazing.
 
I'm keeping your histogram idea at the forefront of my mind too.    -- I'll post over there.

@CA3LE Further on this, can't you make the upload/download be a single stream that cuts off once enough data has been gathered? I don't understand why the multiple steps are needed.
 
(also, if you could chime in on this I'd greatly appreciate it 🙏)
 

I'm trying to compare iWay and Init7 in Switzerland, and in the rankings iWay seems to score twice as fast as Init7, but when you go to the individual stats, Init7 way outscores iWay.
 
Ranking: https://testmy.net/country/ch#isps
#1 iWay: 1811.4 Mbps 2152 Mbps  316 Mbps   47 clients took 356 tests recently #2 Init7: 624 Mbps 871 Mbps  154 Mbps   67 clients took 183 tests recently  
Individual stats:
iWay: https://testmy.net/hoststats/iway, Averages 326.7 Mbps / 85.3 Mbps | 81 ms, last 1000 download: 195.7, upload: 117.4 Init7: https://testmy.net/hoststats/init7, Averages 621.6 Mbps / 227.8 Mbps | 72 ms, last 1000 download: 1265.3, upload: 146.9

I don't understand how these numbers are related? In any case, I think a histogram would be way more useful for the individual stats, it would show the different kind of connections an ISP has.

To do the upload test, it seems to first download data. This can be very slow.
 
Would it not be possible to generate the test data in the browser, with some checksum that has to be different from the last 10000 checksums and is checked on the server?

Update: the upcoming new release has this... I love it!  Renders instantly regardless of the test size or connection speed.   -- it's actually a combination of the current server-side rendering and client-side rendering.  Came together extremely fast once I got on the task actually.  I mean... it's totally instant.  Also saves everyone time and bandwidth, sweet!
 
... the upload test will also include progress.  Works amazingly too.
 
Such an optimal idea, thank you!  PM me if you want beta information.

To do the upload test, it seems to first download data. This can be very slow.
 
Would it not be possible to generate the test data in the browser, with some checksum that has to be different from the last 10000 checksums and is checked on the server?