September 23, 2008

The Hidden Cause of “Slow Networks”

For years the battle cry for networks was "bandwidth, bandwidth, bandwidth!" There just never seemed to be enough to get all data all the time between servers and workstations. File transfers would slow down, email would get hung up, and processes would seem to run slower just because of data getting transferred across networks to complete them.

Technological advances in cabling and networking technology have meant that bandwidth is less of a problem than it used to be -- but the old adage that "an empty space will soon be filled" seems to apply. Given the sheer amount of data being transferred from place to place network connections can still become over-utilized. Most companies have policies that govern network usage, especially during peak hours. During these times, all-employee broadcast messages are usually forbidden, emails with large attachments are frowned upon, and lower-priority processes requiring network resources aren't run.

There can be another cause of slow networks, however -- and it can often cause "ghost hunts" in an effort to solve network problems that factually exist elsewhere. That problem is the fragmentation disease. The illusion happens like this: an employee requests a file from his or her workstation. The file request goes across the network to the server. Because the server has a fragmented drive, access takes overly long. The employee sits drumming fingers waiting. It can even result in a help desk call with a complaint of a "slow network."

Scheduled defragmentation has normally been used to try and handle these issues -- but with today's frantic rates of fragmentation, scheduled defragmentation isn't keeping up. Fragmentation is continuing to occur and impact performance -- including network performance -- between scheduled runs. Another burden is created by the fact that many servers and networks must today run 24X7, and a scheduled defragmentation run is going to heavily impact performance and utilize network resources itself.

Additionally, scheduled defragmentation requires scheduling -- which means valuable IT hours are burned up constantly analyzing and scheduling defragmentation.

The answer to today's rates of fragmentation and resultant network problems is a fully automatic defragmentation solution, one that will run whenever otherwise idle system resources are available. Defragmentation occurs consistently. No scheduling or manual operation is ever required, and performance is constantly maximized.

With fully automatic defragmentation, the fragmentation disease is permanently cured. Once it is in place, you can rest assured that if a network slows down, then it really is the network.

 Contact: Bruce Boyers Marketing Services Email: [email protected]

SOURCE: Bruce Boyers Marketing Services