file system performance

[macleod1021]

I need some help with a file system issue. I have an ISAPI dll that reads files from the file system, processes them and sends the results back to IIS. I developed it on Windows XP and it works beautifully. The process takes 3-5 seconds on my workstation. I then booted my workstation up with Windows Server 2003 R2 and tested the process. It now takes 25-30 seconds.

I ran process monitor to find out what was going on and every time the dll reads a file there's an excessive amount of hits to Security and Security/Default registry keys. This takes about 3-5 seconds per file.

Is there a setting that I can change to get rid of this? I've already given the IUSR user full rights to the directory that it's reading. I've tried excluding the directories from virus scanning, and even uninstalled it for test with no joy. Any help or suggestions would be greatly appreciated.

 

[itsp1965]

Since you are using a workstation to boot a server OS, you'll have to bare the following in mind;

- Memory requirements will be higher and possibly more swapping to disk is involved. Compare how memory is being used especially cache
- The driver for the storage subsystem may need to be upgraded /changed
- Your server OS partition may be fragmented

 

[technome]

Possibly...
Windows server's proformance setting, as a default is set to give prioity to background services, not programs running in the forefront


........................................
Chernobyl disaster..a must see pictorial

http://www.kiddofspeed.com/default.htm

 

[macleod1021]

Thanks for the replys. The workstation I'm using has 4GB ram and it's barely being touched. I've ran all updates on the system that I can find. As far as the partition fragmentation, it's a brand new install. When I said that I booted up Server 2003 R2, I should have worded it I installed Server 2003 R2.

As far as the performance setting, I want the priority to be background services. The process is an ISAPI Extension that runs under IIS.

Some of the steps that I've taken so far include putting IIS in 5.0 Isolation Mode, turning off indexing, shutting down virus protection, uninstalling virus protection.