TE
TechEcho
Home24h TopNewestBestAskShowJobs
GitHubTwitter
Home

TechEcho

A tech news platform built with Next.js, providing global tech news and discussions.

GitHubTwitter

Home

HomeNewestBestAskShowJobs

Resources

HackerNews APIOriginal HackerNewsNext.js

© 2025 TechEcho. All rights reserved.

A bug in Windows 10 could be slowly wrecking your SSD

16 pointsby bobkrustyover 4 years ago

3 comments

boring_twentiesover 4 years ago
Don&#x27;t you love it when you go to reply to a comment but it is deleted by the time you finish writing?<p>Anyway, someone was asking why you&#x27;d <i>ever</i> want to defragment an SSD? Good question, I think. Two things:<p>1. Sequential access is still faster with SSDs, just not by a margin of infinity anymore. I guess this is because of prefetching in the controller of the drive itself?<p>2. To reduce bookkeeping overhead? You need less space to store the information &quot;blocks 1-3&quot; than &quot;block 1, block 17, and block 59.&quot; I have no idea how NTFS works or anything, this is just a guess.
评论 #24321846 未加载
karmakazeover 4 years ago
&gt; Windows 10 is usually able to discern whether to defrag or run a harmless TRIM process on a drive, depending on its type. But if volume snapshots are enabled (so you can revert to a backup using System Restore), it will in fact defrag the drive even if it is an SSD.<p>As was commented in an earlier post of this story: this is only a concern if you have &quot;volume snapshots&quot; enabled.
rkagererover 4 years ago
Defrag scheduling should be under my control, not subject to the whim of some Microsoft idiots pushing out OS updates.