This is the mail archive of the libc-alpha@sourceware.org mailing list for the glibc project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: [PING] [v9] malloc: Consistently apply trim_threshold to all heaps [BZ #17195]


On Tue, Mar 24, 2015 at 03:46:45PM +0000, Mel Gorman wrote:
> On Mon, Mar 16, 2015 at 02:15:17PM -0400, Carlos O'Donell wrote:
> > On 03/16/2015 12:13 PM, Mel Gorman wrote:
> > > On Fri, Mar 06, 2015 at 02:29:34PM +0000, Mel Gorman wrote:
> > >> Trimming heaps is a balance between saving memory and the system overhead
> > >> required to update page tables and discard allocated pages. The malloc
> > >> option M_TRIM_THRESHOLD is a tunable that users are meant to use to decide
> > >> where this balance point is but it is only applied to the main arena.
> > >>
> > > 
> > > Ping as it's been a while since anyone said anything on it. I note it's
> > > in patchwork (http://patchwork.sourceware.org/patch/5496/) but do not
> > > know if that means anyone plans to look at it. Thanks.
> > > 
> > 
> > I actually have a build going with your patch and I'm trying to stress test
> > it to see what impact it has on some real applications.
> > 
> 
> Thanks. Any luck with this?
> 
Is your testing finished?

Also in my opinion M_TRIM_THRESHOLD looks like useless tunable. A better
approach would be do trimming once per second to maximum in previous
second. But that would be separate patch.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]