Install Steam
login
|
language
简体中文 (Simplified Chinese)
繁體中文 (Traditional Chinese)
日本語 (Japanese)
한국어 (Korean)
ไทย (Thai)
Български (Bulgarian)
Čeština (Czech)
Dansk (Danish)
Deutsch (German)
Español - España (Spanish - Spain)
Español - Latinoamérica (Spanish - Latin America)
Ελληνικά (Greek)
Français (French)
Italiano (Italian)
Bahasa Indonesia (Indonesian)
Magyar (Hungarian)
Nederlands (Dutch)
Norsk (Norwegian)
Polski (Polish)
Português (Portuguese - Portugal)
Português - Brasil (Portuguese - Brazil)
Română (Romanian)
Русский (Russian)
Suomi (Finnish)
Svenska (Swedish)
Türkçe (Turkish)
Tiếng Việt (Vietnamese)
Українська (Ukrainian)
Report a translation problem
Small patches for large files.
Let it do its thing.
Steam's patching process does this
1) reads the patch files
2) reads the original file
3) calculates the differences between the two
4) writes out the new file
It is not stopping and starting, its proceeding through these steps. Steam wont download the patch for the enxt file because you are already disk IO saturated while its patching a file.
All of these steps are the worst case scenario for drives. You will never get the 'max' thoroughput of the SSD because your drive is being taxed with non-sequential read and writes. The 'max' is always for sequential reads which again,, you'll basically never get during the patching process.
The patching process is limited by
1) your CPU
2) your disk IO
3) your anti-virus tanking disk IO
You want to read about it?
https://partner.steamgames.com/doc/sdk/uploading
The entire point of patching is to not download everything. For a game like Payday2 would you want to download 80GB of game data for every patch?