dllhost.exe memory size

[Khaled Omar]

I am running a web application with application protection
level set to high, so it runs in a separate dllhost.exe
process, the process takes around 14,000 K of memory I
wanna know if this is fine or I have a memory leak problem

I set all record sets to nothing without closing them and
also I close the database connection

Are there any tools that can measure the ASP page
performance and tell me where do I have performance
bottlenecks ?

Thank You

[Aaron Bertrand [MVP]]

Re: dllhost.exe memory size

> process, the process takes around 14,000 K of memory I[color=blue]
> wanna know if this is fine or I have a memory leak problem[/color]

14 MB doesn't sound like a big problem at all. Is it constantly growing, or
does it stay stable?
[color=blue]
> I set all record sets to nothing without closing them and
> also I close the database connection[/color]

Do you have a reason for this, other than laziness?

ALWAYS close all objects, and ALWAYS set them to nothing. Unless an object
doesn't have a close method (e.g. FileSystemObjec t), there is no plausible
reason to only set it to nothing. There is also never a good reason to just
"not bother" setting an object to nothing. ALWAYS destroy what you create.

--
Aaron Bertrand
SQL Server MVP

http://www.aspfaq.com/

[Khaled Omar]

Re: dllhost.exe memory size

It increases when we use the application and browse more
pages which is normal, it reached 25 MB, when should I get
worried, one other thing, the memory allocation doesn't go
down when I close the browser, when should that happen ?

Thanks[color=blue]
>-----Original Message-----[color=green]
>> process, the process takes around 14,000 K of memory I
>> wanna know if this is fine or I have a memory leak[/color][/color]
problem[color=blue]
>
>14 MB doesn't sound like a big problem at all. Is it[/color]
constantly growing, or[color=blue]
>does it stay stable?
>[color=green]
>> I set all record sets to nothing without closing them[/color][/color]
and[color=blue][color=green]
>> also I close the database connection[/color]
>
>Do you have a reason for this, other than laziness?
>
>ALWAYS close all objects, and ALWAYS set them to[/color]
nothing. Unless an object[color=blue]
>doesn't have a close method (e.g. FileSystemObjec t),[/color]
there is no plausible[color=blue]
>reason to only set it to nothing. There is also never a[/color]
good reason to just[color=blue]
>"not bother" setting an object to nothing. ALWAYS[/color]
destroy what you create.[color=blue]
>
>--
>Aaron Bertrand
>SQL Server MVP
>http://www.aspfaq.com/
>
>
>.
>[/color]

[Aaron Bertrand [MVP]]

Re: dllhost.exe memory size

> worried, one other thing, the memory allocation doesn't go[color=blue]
> down when I close the browser, when should that happen ?[/color]

When the session goes out of scope, probably. You will probably relieve
some of this by using CLOSE + SET TO NOTHING for both recordsets and
connections.

Also, see http://www.aspfaq.com/2424 for other ideas on general efficiency,
and a few on reducing memory footprint of ASP pages.

--
Aaron Bertrand
SQL Server MVP

http://www.aspfaq.com/

[J. Baute]

Re: dllhost.exe memory size


"Khaled Omar" <ko78@hotmail.c om> wrote in message
news:d10801c409 f2$cf36b0a0$a10 1280a@phx.gbl.. .[color=blue]
> It increases when we use the application and browse more
> pages which is normal, it reached 25 MB, when should I get
> worried, one other thing, the memory allocation doesn't go
> down when I close the browser, when should that happen ?[/color]

If you are worried about memory leaks just keep an eye on the memory ussage
of your application while you run through it. Opening new pages ussually
will make the app allocate some more memory, refreshing the same page
however shouldn't, or shouldn't take as much as it did initially.
When you keep refreshing a page, and you see the memory rise with the same
amount with every refresh, chances are you have a memory leak in that page.