Account  |  View Cart  
Condusiv Technologies logo

Condusiv Technologies Blog



 

 

Condusiv Blog: Welcome to the Condusiv Blog

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.

Experts discuss built-in defragmentation and the superior merits of Diskeeper optimization

by Dawn Richcreek 27. January 2012 09:18

Recently, there’s been a lot of talk about built-in defragging systems. Is Windows®7 the best option? In the latest issue of Processor Magazine, experts weigh in, making the case for Diskeeper’s optimization in the enterprise. Read the whole article here: http://www.processor.com/articles//P3402/11p02/11p02.pdf?guid

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

RecentComments

Comment RSS

Calendar

<<  May 2013  >>
MoTuWeThFrSaSu
293012345
6789101112
13141516171819
20212223242526
272829303112
3456789

View posts in large calendar