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.

Crazy or Smart? Inside IntelliWrite part II

by Michael 2. February 2010 05:39

A cure for cancer it is not, but in the category of performance (defrag) software, IntelliWrite is quite the bold, unorthodox step forward. Like many things new and revolutionary it is to be questioned, critiqued and qualified.

When we created IntelliWrite we had to first question the old way of doing things. Same goes for you, the user. You also need to form your own opinion on whether a new approach to eliminating fragmentation is warranted and worthwhile.

Now of course new does not necesarrily mean better, but new can, when done right change the way of things... for the better.

Our customers are our best and favorites critics. We hope we have provided you value and have earned your approval.

IntelliWrite technology is, as the name would imply, smart. Not only is it a better solution to removing fragmentation (it prevents fragmentation), but it actually self-learns; i.e. it gets smarter over time. Or perhaps more simply as one customer, who per his company policy must remain anonymous :-(, said, "crazy smart".


IntelliWrite learns how the various different applications on your system write data, much like advanced heuristic anti-virus solutions that learn "patterns" and can then proactively block new, as yet unreported, malware. IntelliWrite adapts to the applications on your system and how they write, and thereby fragment your files. That adaptive learning makes IntelliWrite increasingly more effective on your computer.  

Another part of the technology is an awareness of its surroundings. IntelliWrite automatically detects conditions where it might affect system performance and backs off, thus providing the best balance for performance – improves performance when fragmentation can be prevented and does not impact free space fragmentation when it might matter (i.e. when the available space is very low). One such easy-to-demonstrate case is on volumes with less than 2GB free space; IntelliWrite disables itself.

We began the process of securing the intellectual property rights to this revolutionary innovation prior to the release. You don't have to be a crazy Irishman to know that if you're looking for "The only way to prevent fragmentation before it happens(tm)", you've come to the right place.



Diskeeper | IntelliWrite

Diskeeper 2010 Administrator edition released

by Michael 15. January 2010 05:48

Diskeeper 2010 Administrator is now complete and available for broad use. You can download trialware from here. For customers previously using the Release Candidate (RC), you can go to your Diskeeper Account page and download your full licensed version. We made numerous user experience enhancements from the RC.

One improved UI example is the new start page:

The new major feature in Diskeeper 2010 Administrator is the “at-a-glance” network-wide overview of disk performance and system health. This network performance dashboard includes access for more details on noted issues and ability to directly initiate tasks such as remote control, deployment, and configuration to quickly remedy the situation. The Dashboard provides important customizable alerts on systems that have:

• Low free space

• Severe file fragmentation

• Extreme paging file or meta data fragmentation

• Failures to defragment or where Diskeeper is not operational

• Product activation expiration

• Diskeeper updates available for installation

The "alerts" are now available for both computers with Diskeeper and those without it. As with prior versions of Diskeeper Administrator, "reports" continue to be available for both systems without and without Diskeeper.

Ops Manager (both MOM and SCOM) Management Packs are included with the Diskeeper Administrator full version. If you require a trial of this solution, please contact our Corporate Sales dept.


Channel | Diskeeper

Diskeeper 2010 is certified for Windows Server 2008R2

by Michael 4. January 2010 05:05

As of December 31st, Diskeeper 2010 is certified. 



The Diskeeper Dashboard - IntelliWrite

by Michael 17. December 2009 11:58

We have an online FAQ that I thought I'd post here as well. It provides some valuable insight into what's going on with all those graphs and statistics related to our proprietary new IntelliWrite technology.

IntelliWrite Fragmentation Prevention


This section of the Dashboard tab explains that IntelliWrite increases system performance by preventing fragmentation before it happens.

IntelliWrite System Statistics for All Volumes Since the Previous Day

This section of the Dashboard Tab includes statistical information regarding fragmentation prevented by IntelliWrite, fragmentation eliminated by Automatic Defragmentation, and a sum of the two numbers since the previous day.

It is important to note that the amount of fragmentation prevented is an estimation determined by a large number of factors and extensive testing. The IntelliWrite graphs are designed to approximate fragments prevented across a wide range of applications and must incorporate various types of file writes and modifications into a singular display. In some cases the charts may over-estimate and in other cases, underestimate. For example, on SQL Server® the graphs may overestimate about 10% of the fragmentation prevented, on Microsoft® Office documents it may underestimate the number of fragments prevented by 80%. What is important is that with IntelliWrite enabled, fragmentation is being handled, before it happens. The end result of having Diskeeper with IntelliWrite and Automatic Defragmentation working is a system running at peak performance in the most efficient way possible (without fragmentation).

The statement: "Proactive prevention is the most energy efficient method to eliminate increased storage power consumption caused by fragmentation," points out that when IntelliWrite is handling your system’s fragmentation, it is reducing the amount of disk head movement previously needed to accomplish defragmentation and therefore is reducing Diskeeper's total system resource footprint.

System Fragmentation Prevention Graph


This section of the Dashboard tab shows system fragmentation prevented by IntelliWrite in real-time. In the graph, fragmentation prevented every second, within the last minute, for your entire system, is displayed in green. The scale on the left side of the graph pertains to the number of fragments that have been prevented and the scale along the top of the graph pertains to the seconds in the last minute.

Statistical Information for Selected Volume(s) Since the Previous Day


This section of the Dashboard tab shows statistical information for selected volume(s) since the previous day. The columns of the table include the name of the selected volume(s), whether or not IntelliWrite and Automatic Defragmentation are enabled, the number of fragments prevented, the number of fragments eliminated and file read/write time % improvement.

Tags: , ,

Diskeeper | IntelliWrite

Fragmentation Prevention - Say Hello to Our Little Friend

by Michael 3. December 2009 12:39

Since the ground breaking release of Diskeeper 2010 I've seen comments that other defragmenters prevent fragmentation.

Ok, so let's technically dissect "how" such a claim may come about...

Does consolidating free space reduce future fragmentation? Yes it helps your odds, but reducing fragmentation and preventing fragmentation are not the same. If you are relying on consolidated free space to offset re-fragmentation you need some luck that the big, or closely located, chunk of free space is where the file(s) being written are going to be placed.


Only ONE free space segment means only ONE place for a file write to go, hence no fragmentation. - That is a true statement, but...

Windows is a robust and dynamic OS. There is a constant and infinite stream of background file writes, modifications and deletions, not to mention all the user generated activity from applications. That makes for a tremendous amount of change in the files and file locations on a volume. Understanding this relentless activity is important because it belies the concept of creating a singular massive chunk of free space as the solution to prevent fragmentation. Any "pretty disk" that gets created (i.e. all files in one area and all the space in another) may look nice in a visual display, but it just doesn't last for more than a few seconds.


You can imagine that attempts to maintain that one massive singular free space area would make for a defragmenter that has to always pack gigabytes of non-fragmented files together with every background deletion/creation event. Busy, busy, busy defragmenter. But hey, a lot of a shiny colors and smiley face emoticons. Yay! 


Now, are there specific benefits to large free space chunks? Absolutely (e.g. shrinking a volume), and Diskeeper provides this too. The key in efforts to consolidate free space into a handful of larger chunks needs to be balanced so that the cost (power usage, wear and tear, system resources, etc...) does not outweigh the benefit (performance). Again, this is the perspective that Diskeeper applies as it optimizes your Windows file systems.   

Now speaking theoretically, if ALL free space were in ONE big chunk, you would be forced to write a file in ONE piece. It couldn't possibly fragment, right? Wrong... 

The bigger issue isn't even about trying to keep some singular giant free space chunk available, because even if you did, there is a more significant obstacle. Windows can write numerous files from numerous processes simultaneously, or more accurately, under the impression of being simultaneous. In reality it is commonplace that some files (File A below) will continue to be held open for writing more data, all the while newer files (Files B & C) start and complete writing all their data. As the first file, which has not yet been "closed", is still being expanded, it has to be written "around" the newer placed files. This causes that first file to fragment around those more recent files that were placed in the way.

This happens ALL the time - your browsers download of a website's many associated files is a perfect example.  

In summary:

Reducing fragmentation is a passive act. Preventing fragmentation requires more than neatly ordered files and free space, it requires a truly intelligent and advanced design that dictates HOW files are written. Only Diskeeper 2010 with IntelliWrite technology offers fragmentation prevention.

So, if you prefer to not leave eliminating fragmentation to chance, given you are spending your hard earned money, and "you wanna play rough [with fragmentation] ok, say hello to our little friend", Diskeeper Twenty-Ten.





Comment RSS

Month List


<<  February 2019  >>

View posts in large calendar