Probably a bad script in the pages.
Try running IISState against the DLLHost(s) when they are causing the
problem:
iisstate -p <pid of dllhost> <enter>
If you need help w/the log, post it to the group.
Pat
"Lluis O" <llob.correobasurano RemoveThis @menta.net> wrote in message
news:eiFx8$Z9DHA.1052@TK2MSFTNGP12.phx.gbl...
> We have an IIS 5.0 / W2K application, and we'are suffering very low
> performance ... we're not talking about hundreds of users connected, but
one
> single user could bring to it's knees the whole server ...
>
> We're only suffering this application ... we didn't develop it, and the
> providers seem to have no idea of what is going on here. We have very
> limited knowledge of it's internals ... and the original developer seems
to
> have dissapeared !
>
> This application is ASP using COM+ .dll's, and when is running, we can
count
> as much as 30 DLLHost process running at the same time. The machine has
> plenty of RAM (2 Gb ... we don't see any shorttage here), and each DLLHost
> consumes about 15 to 50 Mb of memory ... so fa so good ...
>
> But some actions trigered by the user of the application make that -
> generally - TWO of this DLLHost processes began to cope with ALL cpu
> resources of the machine, splitting about 50% cpu each ... and this can
last
> for about one minute or so, during which time the machine performance is
> very, very bad.
>
> So, in my ignorance, it seems to me than in those cases, the problem is
that
> some function hosted in DLLHost-1 is making calls - thousands perhaps -,
to
> some other function hosted in DLLHost-2, and as the calls have to cross
> process boundaries, then most of the time is wasted in the COM+ system
> marshaling the data ... ¿ I'm saying some stupid thing ? I'm very lost
with
> this issue.
>
> ¿ Any one of you can bring me some light ?
>
> Thanks
>
><!-- ~MESSAGE_AFTER~ -->
>> Stay informed about: Simultaneous DLLHost splitting 50% cpu each ... ?