[MLton-devel] yeah, that did the trick

[Stephen Weeks]

> I'm still getting bad behavior (excessive process size, significantly
> larger than physical memory)

During collection the GC will allow itself to have two spaces mmapped
whose total usage is much more than RAM size.  However, one of the
spaces will be new -- it is the "to space" of a copying collection and
not all of the space will be touched during GC, only as much as is
needed to copy live data will.  Once the GC is finished, the "from
space" will be munmapped.  This shouldn't cause paging.

If you are seeing lots of paging, that is bad and shouldn't be
happening.


-------------------------------------------------------
Sponsored by: AMD - Your access to the experts on Hammer Technology! 
Open Source & Linux Developers, register now for the AMD Developer 
Symposium. Code: EX8664 http://www.developwithamd.com/developerlab
_______________________________________________
MLton-devel mailing list
MLton-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/mlton-devel