Add your comments
DLS Archives
May 2013
| Sun | Mon | Tue | Wed | Thu | Fri | Sat |
|---|---|---|---|---|---|---|
| 1 | 2 | 3 | 4 | |||
| 5 | 6 | 7 | 8 | 9 | 10 | 11 |
| 12 | 13 | 14 | 15 | 16 | 17 | 18 |
| 19 | 20 | 21 | 22 | 23 | 24 | 25 |
| 26 | 27 | 28 | 29 | 30 | 31 | |
Essential Windows Apps | Do Not Track | Microsoft Office | SayNow | LibreOffice | Zeam Android Launcher | Dead Space iPhone | Firefox 4 Mobile | Firefox 4 Release | PlayStation iPhone App | Excel Tips | Android Launcher | Google One Pass | Dead Space | Google Cloud Print | Songbird for Android | NBA Jam | Internet Explorer 9 | Windows 7 Connector for Mac | Office Mac 2011 | IE9 RC






Reader Comments (Page 1 of 1)
SmoothMarxApr 11th 2011 11:45AM
Actually, what would be the point of defragging an SSD drive? I thought the memory was flash stored, therefore no needles to go about looking for the info. But I may be wrong. Anyone care to correct me on the matter?
MxxConApr 11th 2011 11:58AM
@__smooth__ you are absolutely correct.
SSDs work with cells/blocks and they always read and write full cell/block at a time. It doesn't matter if your file's blocks are sequential or spread all over the disk. SSD have exactly the same access time no matter which cell you try to read/write.
Furthermore, by forcing SSD to put file's block into a fixed sequence you can potentially undo SSD's wear-leveling algorithm and shorten you drive's lifespan.