I would say, be carefull with GC.Collect() :
http://go-mono.com/forums/#nabble-to26160492|a26160492
2009/11/17 Mike Christensen :
> Thanks! This is exactly what I needed. I did some tests and with a
> large database (probably the most data I'll ever have) I allocated
> about 500 megs on the heap
Thanks! This is exactly what I needed. I did some tests and with a
large database (probably the most data I'll ever have) I allocated
about 500 megs on the heap. Once I null out my "temporary workspace",
GC.Collect() takes about 30ms to run and my process goes back down to
about 18 megs.. If I
And note that GC.Collect() is only a recommendation to the runtime
that now might be a good time to run the GC. The runtime is free to
ignore this call if it so chooses.
(PS Sorry about the top-post. Gmail mobile is not the best for lists.)
On 11/15/09, Michael Hutchinson wrote:
> On Sun, Nov
On Sun, Nov 15, 2009 at 7:04 PM, Mike Christensen wrote:
> Hi all -
>
> I have a program that generates some results, but in order to do so it
> must load a whole lotta stuff into memory for calculations. When this
> is done, I only need the results and not the data in memory. This
> data might
Hi all -
I have a program that generates some results, but in order to do so it
must load a whole lotta stuff into memory for calculations. When this
is done, I only need the results and not the data in memory. This
data might be several hundred megs on the heap or more.
When I'm done, I want t
