Instal Steam
login
|
bahasa
简体中文 (Tionghoa Sederhana)
繁體中文 (Tionghoa Tradisional)
日本語 (Bahasa Jepang)
한국어 (Bahasa Korea)
ไทย (Bahasa Thai)
Български (Bahasa Bulgaria)
Čeština (Bahasa Ceko)
Dansk (Bahasa Denmark)
Deutsch (Bahasa Jerman)
English (Bahasa Inggris)
Español - España (Bahasa Spanyol - Spanyol)
Español - Latinoamérica (Bahasa Spanyol - Amerika Latin)
Ελληνικά (Bahasa Yunani)
Français (Bahasa Prancis)
Italiano (Bahasa Italia)
Magyar (Bahasa Hungaria)
Nederlands (Bahasa Belanda)
Norsk (Bahasa Norwegia)
Polski (Bahasa Polandia)
Português (Portugis - Portugal)
Português-Brasil (Bahasa Portugis-Brasil)
Română (Bahasa Rumania)
Русский (Bahasa Rusia)
Suomi (Bahasa Finlandia)
Svenska (Bahasa Swedia)
Türkçe (Bahasa Turki)
Tiếng Việt (Bahasa Vietnam)
Українська (Bahasa Ukraina)
Laporkan kesalahan penerjemahan
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?