Condusiv Technologies Blog

Condusiv Technologies Blog

Blogging @Condusiv

The Condusiv blog shares insight into the issues surrounding system and application performance—and how I/O optimization software is breaking new ground in solving those issues.

In the beginning...

by Michael 21. May 2009 11:30

A long time ago in a server room far, far away there was the weekend effort of IT to "backup, reformat, restore". Alternatively one could "squeeze" all the data to the front of the disk/volume after taking the volume offline and running special utlities. This was how fragmentation used to be solved. Eventually defragmentation evolved into online Manual and eventually Scheduled tasks. That lasted for years until it evolved again to Automatic and then invisible Real Time defragmentation, for which Diskeeper 2007 through 2009 stand alone. But it is time to evolve once again, stay tuned for the sequel...



Comments (2) -

5/18/2009 3:34:05 PM #

I think the next evolutionary step after the Automatic Defragmentation will be the creation of a filesystem that defragments and maintains itself automatically as required. Some latest linux filesystems, although not quite there yet, are already headed that way (e.g. Reiser4).


7/13/2009 3:51:41 PM #

Really? Are you finally going to fix Windows ntfs driver so that it takes a few cpu cycles to do a better job at file placement? Instead of the current "find the first available cluster, fill it, repeat..."

I'm currently looking for more in-depth details about Diskeeper 2009. Does it prevent windows writing the file and does diskeeper take over to determine a better file placement or is diskeeper still only doing defragmentation. As a concept an afterthought, a cure for a disease.

See my posts about this:

Rudi Larno Belgium

Comments are closed


Comment RSS

Month List


<<  February 2020  >>

View posts in large calendar