Large chunked file transfer, economically better for both Steam company and clients.
Instead of downloading large files in one whole big fat fallible download, try chunking it, and instead downloading smaller chunks, that get verified and held by the client, even when the download as a whole fails. This means less retries and both less bandwidth usage for both the company as well as the client's side, while improving quality. Less retries, less angry people that have to rely on lousy/fallible connections.
I'd say about 1GB to 4GB chunks for maximum file part sizes.
It should not matter how the file as a whole would look or how large it is, just chunk it and retain it, piece by piece and re-assamble as the whole file after download finally yet finishes.
It's better economically for both Steam as a company as well as the people downloading their software.
< >
Showing 1-2 of 2 comments
That's how it already works.
Ettanin 3 Sep @ 12:39am 
Steam uses 1 MB chunks and applies them on the fly. In case of failure, a copy of the unpatched file is temporarily kept.

See also: https://steamdb.info/blog/steam-download-system/

One correction however: Since May 2025, Steam uses zstd instead of LZMA for newer downloads and updates.
Last edited by Ettanin; 3 Sep @ 12:41am
< >
Showing 1-2 of 2 comments
Per page: 1530 50