SOURCE: Bruce Boyers Marketing Services

December 21, 2009 16:58 ET

Fragmentation: Doing It Right the First Time

BURBANK, CA--(Marketwire - December 21, 2009) - "Should have done it right the first time" is a common phrase, usually aimed at someone who, first time out of the box on a project, seemed to get it wrong. Of course, the person uttering this comment is almost always someone that couldn't have done it themselves, and certainly never would have conceived of "how to do it right" until the project or product was already done and it could be easily observed what was "wrong" with it.

A great example was an early racing motorcycle. When the engine was turned on, the throttle was fully open, and the thing just took off. It was easy to look at it after the fact (and probably after a few serious mishaps) and point out that the throttle should be controllable by the rider -- but it's interesting that the bike was fully designed and produced before this was noticed as a problem.

File fragmentation could be viewed in this way, from a number of different angles. For example, it could be said that fragmentation should never have occurred in the first place, that operating systems should have been designed to run without it. But that would be a very uninformed comment, as fragmentation was actually a clever solution to utilizing all the disk space available -- and disk space was horrendously expensive at the time.

The solution to fragmentation became regular defragmentation. Before defrag utilities were produced so that they could be safely run, a disk was defragmented through the backup and restore procedure. The first defrag utilities were manual, and then scheduling came along. It was many years before a fully automatic solution arrived -- and again it could be said that it had finally been done right, and should have been that way to begin with.

But with the announcement of a technology that prevents most fragmentation before it happens, we've finally come full circle. And in one sense, it can be seen that we are actually "doing it right the first time" this time -- for an intelligent feature of this solution makes it possible for files to be written in a defragmented state the first time, preventing a majority of fragmentation from ever occurring.

This solution solves a lot of problems. With fragmentation prevention, system resources are saved in reading files, as well as those saved in writing files in the beginning. Significant savings are also be achieved in energy consumption and cooling -- even more than is done with defrag.

So although it took quite awhile to arrive at this solution, it can be said that in utilizing it we "do it right the first time" every time.

Contact Information