« The latest on Diskeeper support for Vista | Main | Here it is - Windows Vista support »
January 08, 2007
Some More Info on "On-The-Fly" Performance
I want to clear up a few confusions I've seen recently on the internet. Diskeeper 2007 introduced on-the-fly defragmentation for the first time in the Diskeeper product line but, it should be stated, Diskeeper was not the first performance tool to do this.
This "real time" defragmentation has been on our development plate for many years, but it lacked a technological advancement before we could add this into the product. As Diskeeper is one of the highest selling software utilities (usually 7th or 8th, by volume in North America, after Norton AV, Ghost, and antivirus from a couple of the other major vendors) we have a tremendous responsibility. We sell many millions of licenses each year, and a good number of them end up on mission critical servers in the world's largest companies. The product, as it evolved into a truly automatic program, had to ensure that the product offered all the benefits and none of the drawbacks an on-the-fly application might generate, on these massive server systems.
The benefit of addressing the consideration of a high-powered SAN or application server also translates to the small business and home user, as they now get a technology designed for some of the most powerful Windows-based computers in use today. Kinda of like putting a turbocharged sports car engine in an economy car, but still getting the MPGs.
Speaking of car analogies, it brings up another. The following is an article I wrote for the Diskeeper 2007 release, but it seems appropriate to re-publish here... [forewarning: this is a marketing article, not a technical one :-) ]
Introducing a Revolutionary Way to Change Your Oil:
Regular scheduled defragmentation has often been compared to changing oil in your car. An excellent analogy, because if you fail to address this regular maintenance task, eventually the engine breaks down. The same effect occurs on computers system that aren't regularly defragmented; severe fragmentation can lead to reliability problems.
Yes, the best engine is one that doesn't need an oil change/maintenance, but that product has yet to be delivered.
Diskeeper pioneered Set It and Forget It, decades ago, offering a "regular scheduled oil change". It became advanced enough by the time of Diskeeper 10.0 that those oil changes happened without most users aware it was even happening.
This concept of scheduling has become far more commonplace and Microsoft has recently acknowledged the importance of this activity; following our lead.
Manual defragmentation is an unbelievable pain; compare it in proportion to having to change the oil in the car yourself. Sure you may know HOW to do it, but it takes time and effort.
Scheduled defragmentation was far more livable. It could do this for you. However the problem was that you may have had to schedule this maintenance time outside of production time, because it caused some performance hit, or because that was how the technology was developed (i.e. to be scheduled).
Changing your oil involves flushing out all the current fluid. With the built-in this maintenance time is analogous to "down time" or to follow the analogy, your car was parked in a service garage getting processed (rather than you being able to drive it).
When you think closely, scheduled oil changes also do something else non-optimally. They change ALL the oil, not just what needs to be changed. Is it really true that after 3000 miles every oil particle is equally degraded? Unlikely; but to finitely replace only the worn oil and leave the viable oil is technologically improbable (shy of an oil dialysis machine) if not impossible. It certainly doesn't make much sense given that it would be more work to implement this than just toss and replace all the fluid. Synthetic oils allowed you to delay the scheduled oil change until around 7500 miles, but you still have to get the maintenance done.
Now, what if you could replace just the oil that actually needed replacing and save the oil that was still perfectly good? Now, building on that thought, what if you could replace the deteriorated oil exactly when it was degraded (using new technology); and not have to wait until 3000 or 7500 miles?
That would be real AUTOMATIC oil changes; far better than scheduled oil changes. It would be much like the sun coming up every morning - it just happens! How long you have to wait in between oil changes is irrelevant. It simply is no longer an issue.
Diskeeper Corporation's InvisiTasking is that new technology that allows automatic defragmentation to truly be automatic. It's analogous to a kind of on-the-fly engine-attached device to replace only what oil is worn without affecting the engine in any way. InvisiTasking allows defragmentation to evolve from merely "scheduled" into "automatic".
You can now completely eliminate the concept (and bother) of scheduled maintenance all together; end result true AUTOMATIC maintenance, and the absolute least wear and tear possible on the engine (or hard drive), leading to a longer, more productive and reliable life. Sure, it takes a bit of getting used to as it is still a relatively new idea, but I'm confident when you give it thought you'll agree that it is an evolution of the decades old problem of how to go about solving the problems of poor file system performance.
Posted by Michael at January 8, 2007 07:18 PM
Comments
OK that makes a lot of sense but one thing: why does Diskeeper still require 20% free disk space before a volume is declared "healthy"? As I understand it the warning is issued because defrag performance would suffer while performing the "oil change" ... which is no longer required.
Posted by: Ikester at January 23, 2007 05:41 AM
Our company is still on Diskeeper 10, but since we're early adopter of Windows Vista, we decided to move to Diskeeper 2007. However I have a question regarding InvisiTasking. A software similar to BitTorrent is installed on several computers, and I'm wondering if the nature of these P2P applications (creating smart parts of files constantly) will cause negative impact of InvisiTasking? Should we disable InvisiTasking when using the software? Thanks.
Posted by: Jim at March 29, 2007 08:52 PM
Hi Jim,
There won't be any issues with BitTorrent style applications. That is unless you see that the systems continually run at over 60% CPU (and equivalent for other system resources - e.g. Disk). If that is the case (very rare), there are a couple of options. The first is to consider the EnterpriseServer edition, if we are talking about hundreds of thousands of files. The other option is to contact Tech Support for InvisiTasking configuration options.
I doubt that either of these will be needed, as the product, right out of the box should do just fine. Given the design of InvisiTasking and the ability to run Diskeeper throughout the day, it really is a perfect match for these type of constantly-active applications.
As for the earlier question from Ikester, the 20% notification is derived from general disk performance metrics, mostly based on Microsoft recommendations. It won't make the process "suffer", but will mean that it will take longer to complete.
Posted by: Michael at March 29, 2007 10:56 PM
