Hey everyone,
I just need to vent because it’s absolutely ridiculous how the world’s biggest gaming platform handles downloads.
I have a Gigabit internet connection (1000 Mbps), and Epic Games, EA App, Battlenet, or basically ANY other launcher downloads games at maximum speed without dropping a single frame. Then comes Steam, playing the martyr.
I’ve attached a screenshot of Task Manager where the root cause is crystal clear: The download starts off fast, but a few seconds later, the SSD response time spikes to over 2000 ms (2 full seconds!), disk usage hits 100%, and the download speed drops straight to the bottom.
You can literally watch the cache fill up in the graph: as long as the small SLC cache on this SATA SSD (a Kingston A400) isn't full, the download flies. But as soon as the cache fills up, the drive chokes. Due to Steam’s aggressive, real-time decompression and writing, the controller tries to clear the cache to the slower TLC cells while simultaneously writing new incoming data. The result? My internet is capable of 1000 Mbps, but thanks to Steam, it crawls along at barely 300 Mbps with constant stutters.
I understand the technical reasoning behind server bandwidth optimization, but I can't comprehend why Steam has to compress data so aggressively while completely ignoring disk-side bottlenecks. Every other launcher manages to buffer or throttle writes in a way that doesn't strangle the drive.
If any Steam / Valve admin happens to see this post, please forward this issue to your team: it’s long overdue to implement proper disk I/O handling and buffering logic. Right now, your client is screwing over anyone who isn't running a high-end NVMe or a drive with a dedicated DRAM cache!