This web mail archive is frozen.
This page is part of a frozen web archive of this mailing list.
You can still navigate around this archive, but know that no new mails
have been added to it since July of 2016.
Click here to be taken to the new web archives of this list; it includes all the mails that are in this frozen archive plus all new mails that have been sent to the list since it was migrated to the new archives.
On Jan 17, 2010, at 11:31 AM, Ashley Pittman wrote:
> Tuning the libc malloc implementation using the options they provide to
> do is is valid and provides real benefit to a lot of applications. For
> the record we used to disable mmap based allocations by default on
> Quadrics systems and I can't think of a single case of people who needed
> to re-enable it.
It happened to me once. An application couldn't run (not enough memory)
because of the Quadrics stack setting the malloc options.
On Sun, 17 Jan 2010, Barrett, Brian W wrote:
> I'm glad that you've been so fortunate. Unfortunately, I have a large
> application base in which that is not the case, and we have had to use
> mmap based allocation, otherwise memory usage would essentially grow
> without bound. So we go back to the age-old debate of correctness vs.
It would be interesting (though difficult) to know which proportion of
applications are suffering from these settings.
For my part, it is less than 1% (but not 0!).