Diskeeper plans to introduce a file system filter driver to eliminate fragmentation..

[Az7]

PC Magazine (http://www.pcmag.com/article2/0,2817,2351630,00.asp)

[funkydude]

You could also buy a SSD instead and save yourself adding a massive hack between your OS and your drive with system resource impact.

-{ Quote: "The technology may also improve solid-state-disks (SSDs)" }-

I strongly disagree. Any attempt at organizing SSD data is a waste of time and read/writes. Data is SUPPOSED to be spread out all over the SSD to minimize tearing down a specific cell on the SSD.

[Az7]

-{ Quote: "You could also buy a SSD instead and save yourself adding a massive hack between your OS and your drive with system resource impact.



I strongly disagree. Any attempt at organizing SSD data is a waste of time and read/writes. Data is SUPPOSED to be spread out all over the SSD to minimize tearing down a specific cell on the SSD." }-

-{ Quote: "The technology may also improve solid-state-disks (SSDs), which don't typically suffer from the same fragmentation issues that can affect rotating disks, Materie said. SSD performance can far outstrip rotating disks, but only on sequential reads and writes; random writes, in particular, can slow down disk performance. In some cases, a fragmented file being read out to a solid state disc for writing can be treated as a random write, hurting performance, he said. 9Some SSDs use intelligent write algorithms to minimize this.) The Diskeeper technology may help minimize the random-write problem, he said." }-

They are talking about write sequencing technique, to enhance write speed and drive life.. I think their filter driver is just a buffering technique to convert random write to sequential.

[1boss1]

-{ Quote: "I strongly disagree. Any attempt at organizing SSD data is a waste of time and read/writes. Data is SUPPOSED to be spread out all over the SSD to minimize tearing down a specific cell on the SSD." }-

That's true but i don't think they are doing that. I think the data will be still written all over the disk to prevent wear, but files will be stored sequentially all over the disk.

For instance intercept a random file write, and change it to sequential write on the fly so 1234. Then the next file will be still laid on the disk sequentially as 1234 but put somewhere random.

It's hard to say though, the details are pretty sparse.

[Arkham]

-{ Quote: "
Data is SUPPOSED to be spread out all over the SSD to minimize tearing down a specific cell on the SSD." }-

The product in the link addresses filesystem fragmentation that affects the OS regardless of storage hardware. NTFS on an SSD is no different from NTFS on a HDD in this regard.

What you have in mind in internal fragmentation of the SSD, which if I am not wrong, is determined by the SSD controller (Intel/Samsung/etc). IIRC, the X-25 has some sort of internal defragmentation routine as part of the firmware that shuffles data around in the physical cells (blocks), but this is independent of filesystem (de)fragmentation.:)