Read on Twitter
Hi friends of mine that might see this :o
Please don& #39;t do this. SSDs don& #39;t suffer from fragmentation like hard drives do, and Microsoft knows this (hence why there& #39;s a Media Type in this tool). SSDs utilize what& #39;s known as TRIM instead. https://twitter.com/taicheesy/status/1299406444698066944">https://twitter.com/taicheesy...
Please don& #39;t do this. SSDs don& #39;t suffer from fragmentation like hard drives do, and Microsoft knows this (hence why there& #39;s a Media Type in this tool). SSDs utilize what& #39;s known as TRIM instead. https://twitter.com/taicheesy/status/1299406444698066944">https://twitter.com/taicheesy...
"TRIM is just a fancy word for defrag"
TRIM is actually a command sent to the SSD. What the SSD does when it receives it is it begins the process of truly erasing blocks of data no longer in use.
"Wait stuff doesn& #39;t actually delete when I delete it???"
Welcome to computers!
TRIM is actually a command sent to the SSD. What the SSD does when it receives it is it begins the process of truly erasing blocks of data no longer in use.
"Wait stuff doesn& #39;t actually delete when I delete it???"
Welcome to computers!
Without TRIM, your SSD will try to write to all fresh blocks first (great! less wear!). But, when you go to write to a block currently flagged as "not in use", well...
The SSD loses write performance here, because it& #39;s an "overwrite". Overwrites are significantly slower.
The SSD loses write performance here, because it& #39;s an "overwrite". Overwrites are significantly slower.
So, TRIM provides a balance. Fast write speeds into fresh blocks, while performing a weekly sweep to freshen up blocks that are considered no longer in use (e.g. you deleted a file). It doesn& #39;t reorganize files. It doesn& #39;t defragment.
Now, let& #39;s say this was a major problem for some reason. Let& #39;s say the SSD was truly being defragmented. I& #39;ll humor this for a moment because we can talk about defragmentation a bit.
After all, if we read through some of these articles, like one from techradar, it does say that if Volume Snapshots are enabled, it& #39;ll defrag the SSD. So, let& #39;s just run through it.
Defrag doesn& #39;t reorganize the _entire_ drive& #39;s content.
Defrag doesn& #39;t reorganize the _entire_ drive& #39;s content.
What defragmenting a drive _does_, is migrate your files around so you have continuous strips of blocks. This is important for hard drives, since reads and writes both have delays (requiring the drive head to seek).
So, how long has this been happening for? Oh, since about May. So, 3 months or so. So, how fucked are your SSDs?
Well...not really that fucked.
Well...not really that fucked.
Do y& #39;all remember defrag in Windows 95? How it pushed all of your files together with that pretty visualization? Compacting every block next to every other block?
Yeah, Windows hasn& #39;t done that since...XP?
Yeah, Windows hasn& #39;t done that since...XP?
Turns out, the speed gain for compacting every block next to each other wasn& #39;t worth the no-longer realistic amount of time to perform that type of defrag cycle. So, all Windows does now is make sure your files are in contiguous strips.
I have two Samsung SSDs in my machine right now (500GB each), as well as an NVMe boot drive (250GB). Have I been filling up and deleting a shit-ton of data since then?
Well...no. I haven& #39;t even done 250GB of wear on this NVMe drive yet.
Well...no. I haven& #39;t even done 250GB of wear on this NVMe drive yet.
It& #39;s all been things like, oh, temp files, etc.; so, if a full defrag is actually running, well, nothing& #39;s really going to be happening.
If large files have big chunks in them? OK sure, it& #39;s going to want to compact those together, but I& #39;m also not really deleting very many large files either. Unless you& #39;re cycling your Steam library like crazy then OK, sure, the SSD might se higher-than-normal wear.
Now, how can you see how this is affecting y& #39;all? Because seriously, look into this yourself to see if this is a problem!
Open the Event Viewer. Go to Windows Logs, then Application. Click "Filter Current Log", and for an event source, select "Defrag".
Open the Event Viewer. Go to Windows Logs, then Application. Click "Filter Current Log", and for an event source, select "Defrag".
If you& #39;re concerned that the defrag schedule on your machine is running too frequently, then alright, go ahead and disable it for now if you& #39;re really worried. There might be a case where yeah, you might reboot every day and yeah, it& #39;s defragging every day.
But, at the same time, my 250GB NVMe is set up to endure 150TB of writes. 82GB of writes per day, for 5 years.
If the _entirety_ of my used space (62GB) on this NVMe drive were 100% fragmented? Then yeah, I would burn through writes unnecessarily.
If the _entirety_ of my used space (62GB) on this NVMe drive were 100% fragmented? Then yeah, I would burn through writes unnecessarily.
But, 100% fragmented _every day_ for 3 months? It& #39;ll be fine.
ONE MORE: TRIM is performed first, then a defrag. TRIM is normally once a week, defrag once a month.
The short story? Your use of the SSD is still going to trump the amount of wear this& #39;ll cause.
The short story? Your use of the SSD is still going to trump the amount of wear this& #39;ll cause.
Again keep in mind that Win10 defrag is smart; it& #39;s not a full-on disk shuffle, not everything is changing places. Get that Win95 visualization out of here.
