[Mono-list] Garbage collection and memory usage
Miguel de Icaza
miguel at novell.com
Mon Apr 24 18:47:09 EDT 2006
> > > We looked at the problem, and it boils down to the fact that Mono does
> > > not have a compacting GC.
> > After making some tests and googling a lot, I came to the same
> > conclusion. But this only explains why the memory usage is so big, and
> > keeps growing, it doesn't explain why mono "hangs" and .aspx pages are
> > not processed when there is still free memory on the machine.
> I could not reproduce the hang of Mono, but it did expose another
> problem: I get a connection reset by peer while the large pages are
> begin generated, we will investigate.
We investigated this last week.
I could not reproduce the case you describe (memory being available, xsp
stopped responding to requests). What OS are you running, version,
version of Mono and version of XSP/Mod_Mono?
As for the second problem, the one I mentioned: we found that this seems
to be caused by the CPU being too busy with the generation of the return
page to have time to close the dangling sockets.
At least that is what it seems so far (when I used Apache Bench to flood
the machine with requests, which was the only way I would get the reset
Am not sure how Apache copes with this problem, probably they have a
larger listen queue than we do.
More information about the Mono-list