Re: Large file write bogs down server

Tech-Archive recommends: Repair Windows Errors & Optimize Windows Performance

From: MCSEGURU (mcseguruhere_at_aol.com)
Date: 02/08/05 

Date: Tue, 8 Feb 2005 13:55:28 -0500

Performance, Performance, Performance.
Could be networking related, could be Disk I/O related. I would lean toward
Disk I/O. In which case if you need to do this often you should scale your
server to accomadate for it, which is best accomplished by putting your
large file HD on a separate controller sub-system than your system volume.

In the case of the USB device, that was probably mostly I/O wait putting the
pocessor in a hung "system idle" state while writing to the USB "slow"
device.

"tester" <tester@testthis.net> wrote in message
news:110htc595cuprb8@corp.supernews.com...
>I had similar issue, albeit with much larger files, and writing to a
>external USB device. Never found a solution though. I even upgraded to
>usb 2.0. seems the file system was faster than the hardware.
> Could have to do with the cache on the hard disk in use nowadays too.
> NTFS isn't big on write cache. Must be some way to disable though I am
> not familiar. sorry hope it helps to know you are not alone on this one!
>
>
> "jjjdavidson" <jjjdavidson@discussions.microsoft.com> wrote in message
> news:50831F21-13F3-41CB-8985-4E29D91E0B22@microsoft.com...
>> We have an SBS 2003 Standard server supporting 9 workstations, Win XP and
>> 2000. Occasionally I want to copy or move a large (3-4GB) file onto the
>> server from a workstation. When I start the copy, the server grinds to a
>> halt. Although workstations can communicate with each other, any attempt
>> to
>> access the server from a workstation freezes up. Internet access stops,
>> programs using databases on the server crash, the server's own desktop
>> freezes and will not respond. Until the file copy/move is completed
>> (6-10
>> minutes), it's all the server will do.
>>
>> I posted this about a year ago, but wasn't able to get a satisfactory
>> solution; since then, I've simply avoided writing big files onto the
>> server,
>> which is inconvenient, to say the least. Does anybody have any idea why
>> a
>> large file copy should take so much of the server's resources that it
>> altogether stops responding to anybody else? Thanks!
>
>

Relevant Pages