So I have no clue what this article about, I don't think MS would make such a mistake, maybe it is not a real defragmenting, just some hindering stupid used background stuff like bitlocker could lead strange issues in SSD's in the past. This kind of function make possible to keep ssd's alive until it is possible, without wear leveling, the same file would have written in trillion times, while other blocks 1000. Controller should carry out all the necessary function including the balance make it sure the blocks has the same wear leveling, and controller can also give you information about the solid state disk lifespan in percentage (often included), so instead of "defragmenting" the SSD focus to put data where is the best to avoid short life span. I don't understand this article, defrag and ssd? Inside of the ssd there are multiple modules like short term memory controller, and more things. ![]() The "optimize" which Windows 10 does is just a forced TRIM. Then run the windows "defrag" which takes maybe 5 or 10 seconds (too quick for an actual defag) - and it actually calls is "Trimmed" in the progress bar then check again. You can test this by getting a drive map with a 3rd party defragging software such as Ultradefrag, Piriform, defraggler, O&O, etc. ![]() This issue has long since been corrected and it was never an issue in Windows 10. You also had to manually activate TRIM is some cases. When SSDs were introduced Windows 7 and 8 did not properly manage it and defrag did actually try to defrag the SSDs. Yewego said:The article was correct in 2014.
0 Comments
Leave a Reply. |