2 ms·
Nope. Starting at the NIC, it's not "single-threaded." Intel NIC drivers on most platforms service the multiple buffers using several available physical cores.
by KennyBlanken 5y ago
Nope. Starting at the NIC, it's not "single-threaded." Intel NIC drivers on most platforms service the multiple buffers using several available physical cores. Even if it were single-threaded, memory bandwidth over a decade ago was around 3GB/sec.
Download "acceleration" is snake oil and all "acceleration" does is consume unnecessary resources on both ends.
Download "managers" that can queue up a list of downloads, schedule downloads (say for when you're asleep), automatically retry/partial-resume a big download, throttle a download to a low rate, and so on? That's useful for some folks.
Edit: it's written in java. I'm laughing my ass off.
- dspillett 5y ago> Download "acceleration" is snake oil and all "acceleration" does is consume unnecessary resources on both ends. If there are any network bottlenecks, including at the host, that are enough to stop you saturating your own last-mile link with a single stream, that is simply not true. Or if the sending end sets per-stream limits. Downloading multiple streams from the same source can significantly speed up the process. Maybe it often doesn't, but that doesn't make it snake-oil. > memory bandwidth over a decade ago was around 3GB/sec Memory bandwidth is practically irrelevant if the main bottleneck is the remote network or something between you and it.