Εγκατάσταση Steam
Σύνδεση
|
Γλώσσα
简体中文 (Απλοποιημένα κινεζικά)
繁體中文 (Παραδοσιακά κινεζικά)
日本語 (Ιαπωνικά)
한국어 (Κορεατικά)
ไทย (Ταϊλανδικά)
Български (Βουλγαρικά)
Čeština (Τσεχικά)
Dansk (Δανικά)
Deutsch (Γερμανικά)
English (Αγγλικά)
Español – España (Ισπανικά – Ισπανία)
Español – Latinoamérica (Ισπανικά – Λατινική Αμερική)
Français (Γαλλικά)
Italiano (Ιταλικά)
Bahasa Indonesia (Ινδονησιακά)
Magyar (Ουγγρικά)
Nederlands (Ολλανδικά)
Norsk (Νορβηγικά)
Polski (Πολωνικά)
Português (Πορτογαλικά – Πορτογαλία)
Português – Brasil (Πορτογαλικά – Βραζιλία)
Română (Ρουμανικά)
Русский (Ρωσικά)
Suomi (Φινλανδικά)
Svenska (Σουηδικά)
Türkçe (Τουρκικά)
Tiếng Việt (Βιετναμικά)
Українська (Ουκρανικά)
Αναφορά προβλήματος μετάφρασης
Αυτό το θέμα έχει κλειδωθεί 
Κανόνες συζητήσεων και οδηγίες
Αναφορά ανάρτησης
https://steamcommunity.com/groups/SteamClientBeta/discussions/3/3415431214851495540/
You put the library on another disk, even though its internal as well, suddenly problems happen.
Why, idk.
feel free to add comments there by the way. (there is a lot more 'slowing down downloads' threats popping up as of late.
You can try the following, but I doubt any of it will help.
In CMD
Make sure windows update is done (yes windows update can cause issues like this too, idk why or how)
I assume the latest bios firmware, drivers, etc are installed. (it shouldn't matter if it isn't but ... e.e;, this is unpredictable as to why it happens, though it seems to occur more often on windows 11 than older systems.)
Lets just scream about it or something, not sure what to do.
This problem did not arise because of another library. The only drive I used initially was the NVME M.2, thus only one library existed and the downloads would still plummet to 0mb/s.
Well anyway, it sounds like things make even less sense now.
I assume you checked the speed of the SSD, random 4k write speed?
(use CrystalDiskMark to test your SSD's speed)
I assume you also checked the disk activity in task manager / resource monitor?
(if the disk write usage matches the max random 4k write speed, then it is simply completely occupied and unable to do something else, which is why download dropped to 0mb/s)
(but then the question becomes 'what is it doing, and why')
Anyway, other than this I have no clue currently.
NVME -> steam library downloads plummet to 0mb/s then start back up taking more time
However
SSD -> steam librabry has no issues with downloads
how could this be?
TLDR; DISABLE WINDOWS WRITE CACHING TO SPEED UP STEAM DOWNLOADS
TLDR; DISABLE WINDOWS WRITE CACHING TO SPEED UP STEAM DOWNLOADS
write caching isnt something you should disable as it can cause data corruption if you lose power. write caching isn't going to make a dramatic difference in your write speeds unless you absolutely need metric tons of throughput which again, you don't need as a consumer
People need to understand that benchmarks only show theoretical speeds for mostly unrealistic workloads. Steam downloads espeically patching are the worst case scenarios for disk performance and you will never ever achieve these 'theoretical' limits because steam is obliterating the disk.
https://steamcommunity.com/sharedfiles/filedetails/?id=1082209554
Steam can destroy 1gbps connections
Your downloads/patching are limited by
1) your CPU
2) your disk IO
3) your anti-virus obliterating your disk IO performance
4) your ISP
Replying to say this is what fixed the issue for me. I just had to disable that write caching!
Rather, windows has the ability to interface with the hardware's caches. The check enables this cache, allowing your download to speed up, by writing to this cache which is faster first instead. In the mean time the SSD can go read form its cache and write the file as data, which is slower.
By disabling write caching, you disable its maximum speed, and slow your SSD down to a new max speed.
It is because of this your 'graph' looks constant, but the fact is you're downloading averagely a lot slower.
I don't recommend disabling the write cache. And no, its not because of data corruption. (That only happens if it is enabled, and data is still in the cache instead of on the actual storage and power gets cut from the device for whatever reason.)
---
One reason why your speed maybe slower than expected is due to Window's build in download speed limitation.
In the windows registry (see regedit):
HKEY_Local_Machine//Software//Microsoft//Windows NT//CurrentVersion//Multimedia//SystemProfile
Look at the DWORD key 'NetworkThrottlingIndex'
This key by default is set to 'a', which is 10
To unlock your full download speed, you need to set it to ffffffff.
There are a number of other optimizations like this you can do to speed up downloading.
Please look at TCP Optimizer; it maybe easier than registry editting and using several commands.
THIS IS THE FIX THANKS <3
I disabled the windows write cache while steam was still unpacking and went from 3 MB/s to 433 MB/s as soon as i unchecked the BOX. Thanks Microsoft
Here's how, if you're to lazy to Google:
1.Right-click My Computer, and then click Properties.
2.Click the Hardware tab, and then click Device Manager.
3.Expand Disk Drives.
4.Right-click the drive on which you want to turn disk write caching on or off, and then click 5.Properties.
6.Click the Policies tab.
7.Click to select or clear the Enable write caching on the disk check box as appropriate.
8.Click OK.
It does exist and it is. Windows has an OS-level kernel-mode file-system cache in addition to each physical drive having its own hardware write cache.
Windows flushes the OS-level cache on a rotating window and roughly flushes one-eighth of the 'dirty' (i.e. yet to be written) cache entries to disk every second.
As said; the hardware has its own write cache, or rather: native command queue (NCQ) - which is controlled by two settings in Windows: one to enable it, which is turned on by default. And an additional one to disable Windows' built in behavior to force the command queue to flush all pending writes before continuing - which is disabled by default (i.e. the periodic forced flushing is by default enabled.
The OS file APIs force periodic barrier commands to be written to the disk queue after completing certain types of writes, which - even if your file contents may suffer data loss - still guarantees your file system stored on a disk will remain intact when an unexpected power outage occurs. That includes the writes that flow from the OS-level file-system cache.
In essence; if you have an M2 drive and have the OS-level cache enabled, then its slow background flushing will always cause the M2 drive to sing to the tune of the delays enforced by the barrier NCQ commands and slow with it, unless you disable the OS cache; disable Windows' ability to use NCQ commands towards the drive (i.e. you are not actually disabling the drive's own internal use of cache) or enable the disabling of buffer flushing on the drive.
I apologize for the misinformation then and the late reply.
Though from what I read, the important part what I tried to post at least,
(source) https://www.game-debate.com/news/25719/why-your-ssd-is-slowing-down-and-how-windows-write-caching-could-save-the-day
disabling the ncq seems to slow down ssds for some reason.
Various sites on hardware:
https://www.seagate.com/nl/nl/support/kb/how-to-improve-performance-of-an-external-drive-in-windows/
recommend keeping the write caching enabled or recommend enabling it for better performance.
So I am guessing whatever that speed sync is the NCQ commands be the barrier of, its still fast enough.
And if these people who claim that it 'solves the issue' are right (rather than wrong and sacrificing speed for stability), it to me doesn't seem to make any sense why it would speed their devices up or keep the same speed when the caching gets turned off, especially after seeing people test it to confirm things (see the first link I posted).
Edit:
You seem to be knowing a lot more than me on that tech level though and my ESL maybe misintepretting something.I apreciate the explanations you gave here and in various other places.
But to summarize: basically I think they're being psychologically manipulated by a graph.
with ma Samsung 980 (ramless too) i dont have this issue with activated write cache.
So the Problem produced by Steam?
It's M.2 and that's only a form factor, M.2 support USB, SATA and NVMe interfaces.
Finally. Problem solved. I was going crazy here :D
Thank you very much sir or madam