Re: Large file copy performance issue with Windows 2003
- From: Manny Borges <MannyBorges@xxxxxxxxxxxxxxxxxxxxxxxxx>
- Date: Fri, 1 Jul 2005 11:04:02 -0700
Hi I think you are onto a good path.
There are 4 items that are going to infulence performance.
CPU
RAM
Disk subsystem
Network interface.
I would thing that the Disk subsystem is caching to RAM
and hitting a roadblock there.
I would contact Dell or CERC and see if they can shed any light on the
controller, how much cache it has and whether it is write through or write
back caching.
"COERCITAS" wrote:
> Hello Todd and thanx for your quick and informative reply.
>
> I'll try to answer as best as I can your points :
>
> 1) Everything is up to date I think. I fail to find any component not
> running the last drivers.
>
> 2) Same answer, of course. I'll check out if there are any really usefull
> utility with those NICs, I think there are.
>
> 3) Everything is OK with DNS and TCP/IP configuration.
>
> 4) Everything is set to 1000 (full, of course). There is no error while
> connecting nor working, only performance drop box side.
>
> 5) disabling this would prevent me from connecting to the said server with
> TS for example, which may cause many problems the way we are using it...I
> tried nonetheless but except the unability to connect with TS, nothing
> worked better. I didn't read all the documents you linked, will do by the
> way.
>
> 6) Tried this already, didn't change anything.
>
>
> I may add it seems the problem is memory related since it occurs when server
> run out of memory, which happens very quickly when we try to copy large
> files. I guess the system caches data in memory before writing it to disk
> but data come much more quickly than system can write to drives. Behaviour
> may be caused by hard drive failure or RAID failure. I will check all of
> this and keep you updated.
>
>
> By the way, do someone know how to configure memory cache behaviour with
> disks in registry ?
>
>
>
> Regards
>
>
>
> "Todd J Heron" <todd_heron_no_spam@xxxxxxxxxxx> a écrit dans le message de
> news: #rWo6PSfFHA.3124@xxxxxxxxxxxxxxxxxxxxxxx
> > 1) Temporarily disable any real-time anti-virus software to see if that
> > helps, and if it does, re-configure your AV settings to something more
> > appropriate for your environment. Also, in cases of a direct cross-over
> > cable between a client and a server, buy a switch and use regular CAT 6
> > cable.
> >
> > 2) Verify that you are running the latest and the correct network adapter
> > driver. Obtain and install the latest manufacturer driver for the card
> > instead of using one that Microsoft has provided. (also see if the
> > manufacturer has any utilities you can use to check NIC performance).
> >
> > 3) Verify that you can resolve the server name from the client and that
> the
> > client can resolve the server. Check DNS and make sure your server has
> only
> > the correct IP address.
> >
> > 4) Verify the network cards of all clients and servers, switches, hubs and
> > routers are set to the same speed and duplex settings (i.e. 100mb/sec &
> Full
> > duplex). If the hubs or switches have utilities you could use to see if
> it
> > may be logging errors that will help your troubleshoot if it is a patch
> > cable somewhere on the network. If hard-coding the same speed doesn't
> help,
> > then set all devices back to auto-negotiate.
> >
> > 5) The problem may be SMB signing or LAN Manager authentication level. In
> > Windows 2003, default server policy forces all SMB traffic to be digitally
> > signed which seems to cause a problem in some configurations of XP Pro.
> In
> > Local Security Policy (Start > Run > secpol.msc > OK) navigate to security
> > options (Security settings > Local policies > Security) and try disabling
> > the option for Microsoft network server:digitally sign
> > communications(always). Ensure you do this on all machines involved (such
> > as via a GPO for an OU). Run gpupdate /force on the server after making
> the
> > change and do the same on the client machine afterwards.
> >
> > Security settings that can cause a problem with downlevel client access:
> > http://support.microsoft.com/default.aspx?scid=kb;%5BLN%5D;811497
> > http://support.microsoft.com/default.aspx?scid=kb;en-us;823659
> >
> > See also:
> > Slow SMB performance when you copy files from Windows XP to a Windows 2000
> > domain controller:
> > http://support.microsoft.com/?id=321169
> >
> > http://support.microsoft.com?kbid=822219 "You Experience Slow File Server
> > Performance and Delays Occur When You Work With Files That Are Located on
> a
> > File Server "
> >
> > 6) Another possibility involving slowness between XP and Windows Server
> > 2003 computers:
> > New registry entry for controlling the TCP Acknowledgment (ACK) behavior
> in
> > Windows XP and in Windows Server 2003:
> > http://support.microsoft.com/default.aspx?kbid=328890
> >
> > --
> > Todd J Heron, MCSE
> > Windows Server 2003/2000/NT; CCA
> > --------------------------------------------------------------------------
> --
> > This posting is provided "as is" with no warranties and confers no rights
> >
>
>
>
.
- Prev by Date: Re: How to decide to subnet.
- Next by Date: Netlogon 5774 error
- Previous by thread: Re: How to decide to subnet.
- Next by thread: Netlogon 5774 error
- Index(es):
Relevant Pages
|
|
