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.

My last entry

by Helpdesk 11. April 2006 14:07
Regarding my last entry: Someone pointed out (correctly) that the article from Microsoft was not in fact new. I had picked it up on my google alerts and had some difficulty verifying the date it was written. I offer my apologies for the mistake. I also want to point out that some of the commenters on my entry are confused about free space defragmentation. All 3rd party defragmenters defragment free space. Everyone agrees that it needs to be defragmented. The only question is to what degree. Some in the industry have promoted free space "consolidation" or the putting of all the free space into one-pool as an attempt at product differentiation. We disagree with this approach of putting it into one-pool, and always have. Has Diskeeper improved over the years at free space defragmentation? Yes. Should we suddenly switch to "consolidate" free space into one-pool? No. The point of my last post was to point out that the one-pool philosophy is incorrect. Going the extra mile to put all of the free space into one-pool is a waste of resources as it only temporarily creates a pretty disk map. In the article I referenced, Microsoft also endorses a different approach when they state that free space should be in, "a few contiguous portions of the disk." I will let the Diskeeper Product Manager Michael elaborate further.



Comments are closed


Comment RSS

Month List


<<  February 2020  >>

View posts in large calendar