Nemrem vjerovati da su sjebali I to...
EDIT: Scott Hanselman je napisao nekaj o tome:
https://www.hanselman.com/blog/TheRe...ntYourSSD.aspx
Citiraj:
Actually Scott and Vadim are both wrong. Storage Optimizer will defrag an SSD once a month if volume snapshots are enabled. This is by design and necessary due to slow volsnap copy on write performance on fragmented SSD volumes. It’s also somewhat of a misconception that fragmentation is not a problem on SSDs. If an SSD gets too fragmented you can hit maximum file fragmentation (when the metadata can’t represent any more file fragments) which will result in errors when you try to write/extend a file. Furthermore, more file fragments means more metadata to process while reading/writing a file, which can lead to slower performance.
As far as Retrim is concerned, this command should run on the schedule specified in the dfrgui UI. Retrim is necessary because of the way TRIM is processed in the file systems. Due to the varying performance of hardware responding to TRIM, TRIM is processed asynchronously by the file system. When a file is deleted or space is otherwise freed, the file system queues the trim request to be processed. To limit the peek resource usage this queue may only grow to a maximum number of trim requests. If the queue is of max size, incoming TRIM requests may be dropped. This is okay because we will periodically come through and do a Retrim with Storage Optimizer. The Retrim is done at a granularity that should avoid hitting the maximum TRIM request queue size where TRIMs are dropped.
|
__________________
Ryzen 7 5700G
AsRock B550 Pro4
HyperX Fury DDR4 3000MHz (4 x 16GB)
Kingston A2000 1TB NVMe
Intel 660p 1TB NVMe
Fortron Hexa 400W
Random PC case
Proxmox VE
95% of the world is retarded, I'm glad I am the 10%.
HP Elitebook 840 G7
Intel i5 10310U
Corsair Vengeance 2x16GB 3000MHz
SK Hynix P31 Gold 1TB
14" FHD IPS
Zadnje izmijenjeno od: Mario92. 02.06.2018. u 14:08.
|