, but not with a service or IIS-hosted application.
Kamen
-Original Message-
From: Moderated discussion of advanced .NET topics.
[mailto:[EMAIL PROTECTED] On Behalf Of Courtney Smith
Sent: 31 2003 . 16:33
To: [EMAIL PROTECTED]
Subject: [ADVANCED-DOTNET] windows service memory footprint
Thanks to everyone for the replies. I've done
everything short of calling the garbage collector
which has been suggested against both in print and
verbally. As for the SQL solution Russ suggest below,
I think my collection of SQL stored procs that gets
called to create my reports its more
Are you looking at the process virtual memory size or the working set
size? These two will give quite a different picture of what your
process is doing. (It's also sometimes a less than exact science
interpreting this stuff, since measuring a process's memory use is not
always that clear cut -
, July 30, 2003 11:01 AM
To: [EMAIL PROTECTED]
Subject: Re: [ADVANCED-DOTNET] windows service memory footprint
I hope that's true. I've had the same problem with my services, which
are
written in C#. Mine are even worse. I have one that takes up 23 MB. It's
using Remoting, AppDomains, Threads, XML
.NET processes will tend to grow to what looks like an alarmingly large
size unless there is a reason for them to shrink. The CLR does actually
keep track of the amount of memory being used system-wide, and if other
processes start to demand more memory, the CLR will trigger a garbage
collect in
I hope that's true. I've had the same problem with my services, which are
written in C#. Mine are even worse. I have one that takes up 23 MB. It's
using Remoting, AppDomains, Threads, XML, some Reflection also, and
other things, but nothing that I'd think would occupy so much memory.
The reason
