From: Zack Weinberg <zack@codesourcery.com>
To: Jeff Sturm <jsturm@one-point.com>
Cc: Daniel Berlin <dberlin@dberlin.org>, gcc@gcc.gnu.org
Subject: Re: Locality problems caused by size based allocation?
Date: Wed, 18 Dec 2002 00:41:00 -0000 [thread overview]
Message-ID: <87n0n3honv.fsf@egil.codesourcery.com> (raw)
In-Reply-To: <Pine.LNX.4.44.0212172334260.31948-100000@ops2.one-point.com> (Jeff Sturm's message of "Wed, 18 Dec 2002 00:00:54 -0500 (EST)")
Jeff Sturm <jsturm@one-point.com> writes:
> On Tue, 17 Dec 2002, Daniel Berlin wrote:
>> > What exactly is "size based allocation"?
>> What ggc-page does, which is segregate objects based on size rather than
>> age or object type.
>
> Got it. But that puzzles me: the Boehm collector allocates one size
> of object per heap block, fitting your desription of size-based
> allocation, yet there was a measureable improvement over ggc-page?
The Boehm collector may choose better size buckets. Our current
choices are crap, and I have statistics to prove it. (details will
cheerfully be provided, but not now, because I'm not going to sit and
wait for gnumeric to paint its window over this remote X11 session).
Also, I believe it uses a generational algorithm, which should knock
down the large amount of time spent marking live objects.
zw
next prev parent reply other threads:[~2002-12-18 5:38 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-12-16 11:19 Daniel Berlin
2002-12-17 15:47 ` Jeff Sturm
2002-12-17 16:13 ` Daniel Berlin
2002-12-17 20:03 ` Zack Weinberg
2002-12-17 21:01 ` Daniel Berlin
2002-12-17 23:16 ` Jeff Sturm
2002-12-18 0:41 ` Zack Weinberg [this message]
2002-12-18 12:59 ` Jeff Sturm
2002-12-18 5:44 ` Fergus Henderson
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87n0n3honv.fsf@egil.codesourcery.com \
--to=zack@codesourcery.com \
--cc=dberlin@dberlin.org \
--cc=gcc@gcc.gnu.org \
--cc=jsturm@one-point.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).