[MLton] Re: Chat with Wesley Terpstra

[Wesley W. Terpstra]

On Mon, May 3, 2010 at 7:20 PM, Matthew Fluet <matthew.fluet at gmail.com>wrote:

> > I noticed that the no-paging varient took more than 3.6GB of physical
> memory
> > in windows task manager (enough that my system thrashed). I didn't have
> task
> > manager open for the yes-paging test. Perhaps it is overestimating the
> > amount of physical memory and thus not stopping at 50% as it should? Or
> is
> > it the usual last-step resize = up to 2* maximum memory? Whatever is
> > happening, it's not ok to push a system to thrashing with default
> > parameters.
>
> If you really don't want thrashing, then you need to set a "@MLton
> max-heap ??" to your physical memory.  MLton's policy has always been
> to use as much memory as the application requires, subject only to the
> amount of memory obtainable from the operating system (unless max-heap
> sets a lower limit).  MLton will try to size a heap to stay within
> physical memory (really, 50% physical memory with the default
> ram-slop), but if the live size of the application exceeds that and
> the operating system is willing to give over the memory, then MLton
>

I wasn't thinking. You're right, of course.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mlton.org/pipermail/mlton/attachments/20100504/3ec80e5c/attachment.html