This is the mail archive of the
libstdc++@gcc.gnu.org
mailing list for the libstdc++ project.
Re: gcc 3.3 garbage collector defaults
- From: Geoff Keating <geoffk at geoffk dot org>
- To: Mike Stump <mstump at apple dot com>
- Cc: Mike Stump <mrs at apple dot com>, Benjamin Kosnik <bkoz at redhat dot com>, Andi Kleen <ak at suse dot de>, zack at codesourcery dot com, gcc at gcc dot gnu dot org, libstdc++ at gcc dot gnu dot org
- Date: 27 Jan 2003 15:19:58 -0800
- Subject: Re: gcc 3.3 garbage collector defaults
- References: <jmadhmb3zt.fsf@desire.geoffk.org><8F72D7DC-324C-11D7-96B3-003065A77310@apple.com>
Mike Stump <mstump@apple.com> writes:
> On Monday, January 27, 2003, at 02:51 PM, Geoff Keating wrote:
> > I have evidence that on one machine, a two-processor machine with
> > 128Mb of memory, that GCC starts to thrash when it uses more than
> > about 40Mb of memory and two copies are running (this makes sense,
> > 2*40Mb of GCC plus about 50Mb for the system = thrashing). This sort
> > of thing is why I want to try an adaptive approach.
>
> Or, put another way, you have data that supports increasing it to only
> 20MB. I'd just say, well, ok, let's increase it to 20MB then.
Actually, no. On this particular build, the actual working set size
is about 34Mb. So I have data that says that sometimes the right number for
ggc_min_expand is 6Mb or so.
--
- Geoffrey Keating <geoffk@geoffk.org>