Having a lot of trouble here. I'm using Windows Server 2003 SP2. I've installed all the updates and latest .NET versions. I've separated my sites into separate application pools. I have a site that is actually 99% Classic ASP with a couple ASP.NET pages that are rarely, rarely called.
I have dual processors but one is being fully utilized (50% CPU usage). This spike in CPU occurs sporadically but when it occurs it happens until IIS recycles the worker process. I used Process Explorer and narrowed the thread causing this by sorting the offending w3wp.exe's thread list by CSwitch Delta; the thread is referencing:
mscorwks.dll!CreateApplicationContext (+ some offset)
I have run numerous tools like IISTracer, IISPeek, etc to see if there is a page running that is taking a long time. None of those report any pages running while the CPU is being pegged. In fact, using LogParser to determine what pages are running the longest doesn& ...
Go to the complete details ...