The NTFS file system is the heart of the Windows O/S and its performance is directly related to system reliability. However, NTFS writes files to the disk in scattered pieces, even if the disk is almost empty. This immediately multiplies the amount of I/Os it takes to complete a task and quickly creates a decline in even the newest and most advanced systems.
Slows, crashes and frequent downtime impact productivity and the effects are felt throughout the company.
File server performance optimization achieves two important objectives: minimizing downtime and increasing speed and efficiency of applications. High traffic, typical of most servers, will bring about a loss of performance quickly when a server has an underlying NTFS performance issue. The problem is that system management and monitoring tools may only narrow the cause down to a range of possibilities. Possible solutions often do not state splitting of NTFS files, because the effects of unnecessary I/O are commonly underestimated.
Learn about The shift to I/O optimization to boost virtual and physical server performance »
How should I optimize my File Server performance?
Excessive I/O is often the "straw that broke the camel’s back" when noting issues of stability or reliability. Stressed I/O activity, compounded by split files, can expose faulty device drivers or file filters that may otherwise operate effectively (in non-fragmented environments). The reliability of third-party applications is highly dependent on the degree to which those applications can accommodate bottlenecks, such as in disk subsystems.
System administrators have tested V-locity® I/O optimization software and found the resulting file server performance to be so consistently maintained at peak levels that major system and network problems disappear. In two cases a SQL administrator discovered the Average Disk Sec/Read was very high on their database servers.
A clue that you should evaluate file I/O optimization is when you get a recommendation to increase I/O bandwidth, such as adding more disks, i.e., your SAN vendor tells you to add another controller or array. V-locity will provide better results: it actually fixes the issue and prevents it from happening again rather than masking it—and it’s a much more efficient solution than adding hardware.
Download a trial of V-locity and put it to the test in your real-world environment »