Committed Memory issue

[Steven]

We currently have a W2000 server, IIS 5.0, and 1.0.3705 Framework. Our
asp.net app seems to be running well, sometimes kinda slow. We're concerned
with the fact that our committed memory reaches 1.5 GB. Can this be
considered normal? Is there a standard we can go by to make sure things are
running well? What could I check either in my app, IIS configuration or
others to prevent memory leaks?

Any help will be appreciated!

TIA

[Karl Seguin]

Steven,
It's hard to make general assessment, but chances are you are seeing some
type of leak. Or the data you are loading has a huge footprint and you are
caching it too agressively. Does the worker process come close to recycling
itself at this point? Do you start to see some bad exceptions? (ie,
OutOfMemory). In any case, doing an audit is probably a smart thing to do.
It's kinda a tricky thing, but two resource I use when analysing these
problems are:

http://blogs.msdn.com/akhune/archive...11/153734.aspx
and
http://blogs.msdn.com/yunjin/archive.../27/63642.aspx

They take you pretty much through the hole process.

For a memory profiler, check out:
http://www.scitech.se/memprofiler/
and/or
http://red-gate.com/code_profiling.htm
which both have full functional time-trials.

The first step though, as outlined in the first link, is to figure out if
you have a leak, and if so whether it's managed or unmanged. this can
easily be done by setting up the right counters and examing them...

Hope this sets you in the right direction..

Karl
--
MY ASP.Net tutorials
http://www.openmymind.net/
"Steven" <St****@discussions.microsoft.com> wrote in message
news:3C**********************************@microsof t.com...

We currently have a W2000 server, IIS 5.0, and 1.0.3705 Framework. Our
asp.net app seems to be running well, sometimes kinda slow. We're concerned with the fact that our committed memory reaches 1.5 GB. Can this be
considered normal? Is there a standard we can go by to make sure things are running well? What could I check either in my app, IIS configuration or
others to prevent memory leaks?

Any help will be appreciated!

TIA

[Steven]

Thanks alot for such a quick response! I'll look into this to check it out!

Thanks again!

Steven

"Karl Seguin" wrote:

Steven,
It's hard to make general assessment, but chances are you are seeing some
type of leak. Or the data you are loading has a huge footprint and you are
caching it too agressively. Does the worker process come close to recycling
itself at this point? Do you start to see some bad exceptions? (ie,
OutOfMemory). In any case, doing an audit is probably a smart thing to do.
It's kinda a tricky thing, but two resource I use when analysing these
problems are:

http://blogs.msdn.com/akhune/archive...11/153734.aspx
and
http://blogs.msdn.com/yunjin/archive.../27/63642.aspx

They take you pretty much through the hole process.

For a memory profiler, check out:
http://www.scitech.se/memprofiler/
and/or
http://red-gate.com/code_profiling.htm
which both have full functional time-trials.

The first step though, as outlined in the first link, is to figure out if
you have a leak, and if so whether it's managed or unmanged. this can
easily be done by setting up the right counters and examing them...

Hope this sets you in the right direction..

Karl
--
MY ASP.Net tutorials
http://www.openmymind.net/
"Steven" <St****@discussions.microsoft.com> wrote in message
news:3C**********************************@microsof t.com...

We currently have a W2000 server, IIS 5.0, and 1.0.3705 Framework. Our
asp.net app seems to be running well, sometimes kinda slow. We're

concerned

with the fact that our committed memory reaches 1.5 GB. Can this be
considered normal? Is there a standard we can go by to make sure things

are

running well? What could I check either in my app, IIS configuration or
others to prevent memory leaks?

Any help will be appreciated!

TIA