Date: Wed, 23 Oct 2002 12:13:56 -0700 From: David Schultz <dschultz@uclink.Berkeley.EDU> To: Poul-Henning Kamp <phk@critter.freebsd.dk> Cc: Danny Braniss <danny@cs.huji.ac.il>, freebsd-hackers@FreeBSD.ORG Subject: Re: malloc Message-ID: <20021023191355.GA728@HAL9000.homeunix.com> In-Reply-To: <44584.1035399419@critter.freebsd.dk> References: <20021023185024.GA468@HAL9000.homeunix.com> <44584.1035399419@critter.freebsd.dk>
next in thread | previous in thread | raw e-mail | index | archive | help
Thus spake Poul-Henning Kamp <phk@critter.freebsd.dk>: > >A harder problem to solve is fragmentation for long-running > >servers, where the RSS tends to creep upwards over time as virtual > >memory fills with holes. > > This is where you want to run phkmalloc with the 'H' option. > It practically makes it a non-issue last I tried. Perhaps phkmalloc could be made self-tuning with regards to 'H'; I doubt many people know when to use that feature. For example, you might have a heuristic where phkmalloc detects that the program has been running for a long time or has called malloc() and free() many times, so it starts using madvise() on some free pages. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20021023191355.GA728>