I recently took a Linux server (RedHat 9 with stock SAMBA 2.2.7) and a PC running Windows XP and tried to track down a speed problem. It was my contention to start with that some patch or hotfix from Microsoft was destroying the performance. I started with a stock XP install without SP1 or any other patches and timed some accesses to the server. I then installed a patch, rebooted, tried again. I intended to go through each and every patch to find the culprit. After only a half dozen or so lunchtime rolled around and I left. When I came back the PC was agonizingly slow.. What the? This was one PC out of a batch of a dozen or so we were scheduled to install at a clients in a few days. Not knowing about the test I was performing one of the other guys installed Norton Antivirus 2004. Launching a custom Visual Basic app from the server that we write/support took barely <1 second before and upwards of 5 seconds afterwards. Incredible difference. I knew most antivirus software slowed things down _some_ but I was not prepared for this drastic of a difference. Incredible... We de-installed Norton and for kicks installed the one from www.free-av.com
and the speed difference was barely noticable. Perhaps a second to launch that app now, not much more than that.
Anyway, some of the things I did prior to starting this Windows patch install fest:
1) Remove QOS Packet Scheduler. Not so sure now upon reflection if this is necessary or not, someone test with and without while copying to/from a SAMBA server and report back on the speed please. My thoughts are that it affected access to a SAMBA server much worse than to another Windows PC. Figures...
2) Stop the webclient. "webclient" is a service whereby all remote directory/file accesses are attempted as a web request "just in case" this might be a web-shared Microsoft resource or some such(?). It hits the server on TCP ports that SAMBA doesn't pay attention to and has to time out, causing a slowdown. Port 445 TCP comes to mind and in testing SAMBA 3.0 I noticed it did respond to requests to this port. I think the "webclient" hits port 80 as a sort of web request though. Stop it in services graphically or from a DOS shell via "sc stop webclient"