Speed tests
We race WDM against other download managers on a test server built to misbehave: it slows down, drops the line, stalls and lies. Every result is public, including the ones we lose.
Time to a finished file
In seconds, the middle result of 7 runs. Shorter is faster.
A server that keeps dropping the line, 100 MiB
WDM0.142 s
aria2-next0.216 s
A server that stalls, 100 MiB
WDM0.169 s
Surge0.199 s
A server that drips data slowly, 10 MiB
WDM0.295 s
Gopeed0.316 s
| WDM | Best competitor | |
|---|---|---|
| Correct files | 175 / 175 runs byte-exact, 0 wrong names | Gopeed: 14 corrupt files · Surge: 1 |
| Crash test: 1,000 × kill -9 | 0 corrupt, 0 duplicates (1,584 downloads) | not measured by anyone else |
| CPU per GiB (1 GiB file) | 1.26 CPU-s | 1.51 CPU-s (aria2c, 16 connections) |
| Flaky server, 100 MiB | 0.142 s, fastest | aria2-next 0.216 s |
| Stalling server, 100 MiB | 0.169 s, fastest | Surge 0.199 s |
| Slow-drip server, 10 MiB | 0.295 s, fastest | Gopeed 0.316 s |
| Real CDNs (kernel.org/Fastly, Google, Mozilla) | no competitor significantly faster · lowest CPU on all three | aria2-next, Mister DM, aria2c -x16 |
How it is measured
- Each case runs 7 times and is compared with a Mann-Whitney U test (p < 0.01).
- Time stops when the file is safely on disk, for every client: WDM syncs its files before calling them done, and the benchmark syncs the other clients' files too.
- That safety costs a few milliseconds on small files: wget can finish a 1 MiB file 5–9 ms sooner. The rules allow up to 10 ms on files of 4 MiB or less, and every report lists where that applies.
- Competitors: curl, wget, aria2c, aria2-next, Mister DM, Surge, Gopeed.