Why defragmenting solid state disk is recommended suddenly? What has changed?
>>109778040Why do you people only post mildly nervous Pepe?
games
>>109778045?
>>109778056Games
>>109778040recommended by who? AI generated articles? you'll just wear out your sdd for an imperceptible gain
>>109778235You are dummy, all reputable solid state disk has build in defragmentation algorithms and they running without your knowledges.
>>109778056>>109778109Your posts keep getting truncated. I'll help: are for children*
>>109778264they're not running passes on the entire disk you retard
>>109778305You are pajeet and cannot read properly. Get help.
>>109778283Games are for children. What’s changed?
>>109778321>You are dummy>they running>knowledges>You are pajeet
>>109778076I look like this
>>109778040The lifespan of SSD is way longer than expected, so people don't need to buy a new one often enough, and that's a problem for manufacturers. So now they recommend to defragment it, so it dies quicker, and so you have to buy a new one.The only purpose of a company is to make as much money as possible.
>>109778040Technically while SSDs don't suffer from seek times the same way HDDs do, the filesystems on them do, as telling the SSD to read 1 file split into 200 parts needs 200 commands to be given to the SSD, and while that's still much faster than an HDD there's an obvious CPU side latency cost. And yes the OS can't tell the SSD to remap the logical addresses involved without a flash level copy, because the faggots didn't expose such a function.
>>109778264Probably not quite what you're expecting.>>109778040I think it would come down to the size of erase blocks increasing as density increases.On flash memory, to update or rewrite a sector you have to erase an entire block which is some multiple of sectors, 16, 32, 64, 128, 512, it depends how dense it is.So if you have multiple different files with sectors in an erase block and you delete or change one file, you have to erase and reprogram that entire block with all the sectors, and every block that file has sectors present in.It makes sense to minimize the number of files per erase block, because programming is what wears out blocks on the flash memory, and defragging the SSD would accomplish this by making files more contiguous where possible.But the controllers are also generally trying to do this as files are written, better to keep files contiguous to begin with than fix it later.
>>109778264>>109778040Your SSD is running FRAGMENTATION on your data because it's actually faster to read and write when it's multiple chips. And it moves data around in the background for wear leveling and and out of the write cache (regular cells used as SLC). Defragmentation literally doesn't do anything on SSDs because SSDs don't even expose the physical location of the data on the drive.
>>109781364In simple terms: An SSD can look **“fragmented” internally**, but that’s not the same thing as fragmentation on a hard drive. - **Hard drive:** Files are stored in specific physical spots. If a file is split into many pieces, the drive’s read/write head has to physically jump around. Defragmentation can help by putting those pieces together.- **SSD:** There are no moving heads. The SSD’s controller decides where the data actually goes across its many memory chips.- The SSD may **split data across multiple chips** because that can let the chips work in parallel, making reads and writes faster.- The SSD also **moves data around automatically** in the background to spread out wear evenly. This is called **wear leveling**.- SSDs also use some of their normal flash memory as a faster **SLC cache**, and data gets moved between the cache and the regular storage.- Your operating system generally **doesn't know the actual physical location** of the data inside the SSD. It sees a logical block address, and the SSD's controller handles the physical placement. So, **traditional defragmentation isn't useful for an SSD**. You can't meaningfully tell the SSD, “put all these pieces next to each other,” because the SSD itself controls where those pieces physically live. A better mental model is: > **HDD:** “Put the pieces next to each other so the mechanical arm doesn't have to jump around.”\> **SSD:** “The drive itself decides where to put the pieces, and it constantly rearranges them for speed and longevity.” One small correction: saying SSDs “are running fragmentation” can be misleading. **Fragmentation as seen by the filesystem can still exist**, but it usually doesn't cause the same performance problem it does on a hard drive.
>>109780859Since there is multiple NAND chips akin to multiple layers spinning disks, defragmenting on chip level make sense, it could improve speed since SSD still read from sector one to last sector (sequential read) they can’t jump around sector randomly as fast as they please.
>>109778040They should be called SS Ds. You don't defrag dead space anon, oh wee what cool past-time. My name for it.
