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
Optimizing works about the same, it merely pushes the data close together, which can speed up loading times dramatically.
"Since SSDs have no moving parts, hence “Solid State”, there's no seek time or rotational latency. Instead, SSDs access flash memory (NAND) at much higher speeds, typically less than 50us—that's 50 microseconds, or compared to a typical hard drive with a 15ms average access time, about 300 times faster. But there's more to the story than just speed."
"Because of the way SSDs work, not only does data not become fragmented, but running a defragmentation utility will actually burn through the program/erase cycles and potentially cause premature 'death' of your SSDs. It's not something that would happen quickly—a 500GB Samsung 850 Evo as an example is rated for 150TB of total writes, or the equivalent of writing to every block of the drive at least 300 times. With typical users writing less than 20GB per day on average, it would require more than 20 years to burn through 150TB of writes. But defragmenting could easily write hundreds of GB of data, which would wear out an SSD much faster."
There are no seek times on SSD drives. All data is accessed at the same speed. And it appears it's unhealthy to do too much data moving/writing. Optimizing is the same as defragmenting.
Please, try not to just totally misconstrue my words to make me easier to attack. Get a life.(get me one while you're at it)
It could be playing around with compressed files and putting contents from multiple compressed containers to a single container so that the PC needs to do less work when accessing it, but it's a very far fetched guess and a simple defrag is far more likely.