Steam telepítése
belépés
|
nyelv
简体中文 (egyszerűsített kínai)
繁體中文 (hagyományos kínai)
日本語 (japán)
한국어 (koreai)
ไทย (thai)
Български (bolgár)
Čeština (cseh)
Dansk (dán)
Deutsch (német)
English (angol)
Español - España (spanyolországi spanyol)
Español - Latinoamérica (latin-amerikai spanyol)
Ελληνικά (görög)
Français (francia)
Italiano (olasz)
Bahasa Indonesia (indonéz)
Nederlands (holland)
Norsk (norvég)
Polski (lengyel)
Português (portugáliai portugál)
Português - Brasil (brazíliai portugál)
Română (román)
Русский (orosz)
Suomi (finn)
Svenska (svéd)
Türkçe (török)
Tiếng Việt (vietnámi)
Українська (ukrán)
Fordítási probléma jelentése
But you go ahead and fill up your SSD if you have one and see how that goes
SSDs are not the same as HDDs when it comes to filling them up
in order for TRIM to properly work the SSD needs an amount of free space
The drive was labeled 250GB, when I open C:Properties it says capacity is 238,783,819,776 (222GB). Used space is 142GB and FREE 79GB. I just uninstalled RUST since I hadn't played it in awhile now. My drive now has 97.5GB FREE.
This is a pre-built system from Alienware. When I looked in my add/remove programs I see some other apps and such, but nothing large in file size. So mostly Windows, AC:O. That seem right in terms of usage? Why is the drive capacity labeled at 238 when its a 250gb drive?
I could utilize the move drive option. I do have a 2TB backup drive on the system and I only have DOOM on it. Does the move function in steam work ok?
Just go in the Settings/Download/Library Folders section and create a directory on the HDD, then any games you install will have that location available to install to
Disk Cleanup doesnt affect restore points
Well this is a simple issue, that has some history behind it and too much momentum for a reasonable fix.
Storage manufacturers state 250GB as 250,000,000,000 bytes. Which is correct, those prefixes are used in the decimal (base10) system where kilo = 1,000, mega = 1,000,000 and so on. But Windows displays available space based on base2, so kilobyte is 1,024 bytes, and a megabyte is 1,024 kilobytes and so on.. We've been doing it for so long that's just the way it is. And when we were just dealing with KB, MB and single digit GB it wasn't really noticeable, the numbers weren't unbearably off. But once you get up into hundreds of GB and into TBs those values diverge more and more.
I mean 1KB is only 24bytes off according to the proper meaning of kilo. But 1MB compared between base10 and base2 is 48,576 bytes off. And by the time you get up to hundreds of GB you're several GB off. At 500GB you're about 35GB off. At 1TB about 69GB off and at 2TB about 140GB off.
The actual factual correct terminology, that's never going to catch on, and we'll be answering these GB/TB disparity questions forever is kibibyte, mebibyte, gibibyte, tebibitye where the bi informs you that it's a base2 value.
And so now we live in a world where decimal prefixes sometimes mean 1,000 or 1,024 and that's as shoddy as having a new set of terms no one is interested in using... but here we are.
I wonder if kilo²byte would catch on easier....
Take into account that filesystem metadata also occupies some disk space.
Try to reread my message and probably you'd understand what I said. I said you need to have at least 15% free space (preferably 25-30% to avoid SSD performance degradation).
Easy to understand, right? But it seems you're a writer, not a reader.
Okay and?
You complained about me saying around 30GB or so
he has a 250GB SSD
Do tell me what % that is
Not far off from my opinion of at least 30GB
take your own advice
id also like to point out i wasnt even replying to your initial message, to be honest i didnt even see it, i was giving MY opinion of which you then wanted to accuse me of giving misinformation even though it wasnt directed at you
so from my perspective you were dismissing what i said randomly for no reason
So yeah, seems you may need to read better as well
Go by the free space in GB for your OS SSD, to ensure trim can all work properly and that the OS has room to grow as needed.
Now for a HDD yes you basically must abide by %, which is 10% if not mistaken, as this % is what is required minimum to allow disk defrag to run/take place as needed.
Honestly you should just buy an additional game drive. The fuller the ssd, the less space it has to shuffle the deck of cards behind the scene, the more write amplification is a thing. If you value up time, don't fill your boot drive. A full secondary game ssd doesn't matter because games hardly write at all, and they are cheap as chips now. Games don't benefit much from a faster ssd, and honestly I'd suggest almost half empty for a boot ssd that small.