You can try changing session management. If currently you have InProc
sessions, change to OutProc and see if it helps.
Just use Perfomance counter and profiling tools to understand what happens
and find out the spoiled code place
WBR, Michael Nemtsev [.NET/C# MVP].
My blog: http://spaces.live.com/laflour
Team blog: http://devkids.blogspot.com/
"The greatest danger for most of us is not that our aim is too high and we
miss it, but that it is too low and we reach it" (c) Michelangelo
K> When we have around 40 users, the aspnet_wp jumps to 100% CPU
K> and all screens lag for 30 seconds or more (all on LAN). How do I
K> tell if this is due to settings in IIS or machine.config, or if it is
K> due to bad code? These are all the same page being brought up, with
K> different information from SQL (customer name, phone, address). This
K> is for a call centre environment.
K> I have tried fiddling with IIS and machine.config settings, but
K> nothing I try seems to help. 40 users on a local web server with
K> basic customer information pages should not do this.
K> HP DL380 3.4GHz single processor (same issues on 2.4GHz dual
K> 4 GB RAM
K> Win2000 Server
K> MS SQL2000
K> IIS 5.0?
K> ASP.NET 7.1?
K> Kris Kauth