dllhost getting hammered for memory

dllhost getting hammered for memory

am 25.07.2007 16:26:57 von s_m_b

Our intranet (classic asp + perl) runs on a fairly old W2k box, and
recently, the performance is suffering through what looks like a memory
leak via dllhost.
I've been through the code and made sure its watertight for unclosed
objects.

Two things give me a particular problem.
1) more than one copy of dllhost is running, but nothing is in isolation
modea and only one web site is running.

2) a number of sessions talking to the database server can be seen via the
tcpip window on process explorer. As all comm objects get killed off within
the code, this should not happen?

Re: dllhost getting hammered for memory

am 25.07.2007 20:45:20 von patfilot

How are you measuring memory consumption? The best way is to use
Perfmon:Process:Private Bytes. Watch that and see if your DLLHost is in
fact increasing in its memory use.

Pat
"s_m_b" wrote in message
news:Xns99789D57E9B90smb2000nshotrmailcom@207.46.248.16...
> Our intranet (classic asp + perl) runs on a fairly old W2k box, and
> recently, the performance is suffering through what looks like a memory
> leak via dllhost.
> I've been through the code and made sure its watertight for unclosed
> objects.
>
> Two things give me a particular problem.
> 1) more than one copy of dllhost is running, but nothing is in isolation
> modea and only one web site is running.
>
> 2) a number of sessions talking to the database server can be seen via the
> tcpip window on process explorer. As all comm objects get killed off
> within
> the code, this should not happen?

Re: dllhost getting hammered for memory

am 09.08.2007 16:50:44 von s_m_b

"Pat [MSFT]" wrote in
news:80494658-6801-4282-896E-1688F0ABAE8D@microsoft.com:

Eventuially fond the answer, but its weird.

Two folders on the web site, via IIS, were set to 'high/isolated' for app
protection.

Each copy of dllhost running was linked to one of these, and the last was
to 'eveything' else


> How are you measuring memory consumption? The best way is to use
> Perfmon:Process:Private Bytes. Watch that and see if your DLLHost is
> in fact increasing in its memory use.
>
> Pat
> "s_m_b" wrote in message
> news:Xns99789D57E9B90smb2000nshotrmailcom@207.46.248.16...
>> Our intranet (classic asp + perl) runs on a fairly old W2k box, and
>> recently, the performance is suffering through what looks like a
>> memory leak via dllhost.
>> I've been through the code and made sure its watertight for unclosed
>> objects.
>>
>> Two things give me a particular problem.
>> 1) more than one copy of dllhost is running, but nothing is in
>> isolation modea and only one web site is running.
>>
>> 2) a number of sessions talking to the database server can be seen
>> via the tcpip window on process explorer. As all comm objects get
>> killed off within
>> the code, this should not happen?
>
>