DLLHOST looping at 50%! What does this tell me? -- inetserver asp components

Larry Woods
8/18/2003 9:19:19 AM

I have a bug somewhere and I don't know how to find it. I was told by
someone that they thought that one of my ASP pages might be looping. Well,
I set up a test and (1) a tight loop buries the CPU; DLLHOST=100%, not 50%,
and (2) when the page timed out, the page was closed and the DLLHOST process
time went back to 0%.

Now, I also have a component (VB-based; calculations only) that I
instantiate which could also be causing the loop but, again, doesn't IIS
clear the dll when the session terminates?

TIA,

Larry Woods

Pat [MSFT]
8/18/2003 12:33:24 PM

Since ASP pages run on a single thread (i.e. each page gets a separate
thread), the # of procs will affect the results of a test like this.

On a single proc, the CPU usage will go to 100%
On a dual proc, the CPU usage will go to 50 (100/2).

etc.

Pat

[quoted text, click to view]

inetserver asp components : DLLHOST looping at 50%! What does this tell me?