From: skaller <skaller@users.sourceforge.net>
To: Markus Mottl <markus.mottl@gmail.com>
Cc: Nathaniel Gray <n8gray@gmail.com>, ocaml <caml-list@inria.fr>
Subject: Re: [Caml-list] Cost of register_global_root (was: Stopping a value from getting GC'd)
Date: Fri, 19 Aug 2005 03:13:21 +1000 [thread overview]
Message-ID: <1124385201.8402.10.camel@localhost.localdomain> (raw)
In-Reply-To: <f8560b8050817205775375b11@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 732 bytes --]
On Wed, 2005-08-17 at 23:57 -0400, Markus Mottl wrote:
> On 8/17/05, Nathaniel Gray <n8gray@gmail.com> wrote:
> > One thing that the FM doesn't mention is how expensive it is to
> > register a global root. Can I register thousands of them or will
> > there be performance problems?
>
> There is a severe performance penalty for registering many thousands
> of roots as I have seen in one of our applications. AFAIK, they are
> scanned at each minor collection. This will drive up CPU-usage even
> if your program doesn't do much otherwise. Maybe the GC could be
> improved in that area.
Why not just put the pointers into a (reachable) hashtable?
--
John Skaller <skaller at users dot sourceforge dot net>
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2005-08-18 17:13 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-17 4:12 [Caml-list] Stopping a value from getting GC'd Jonathan Roewen
2005-08-17 5:36 ` Bardur Arantsson
2005-08-18 1:31 ` Cost of register_global_root (was: Stopping a value from getting GC'd) Nathaniel Gray
2005-08-18 2:40 ` [Caml-list] Cost of register_global_root Alain Frisch
2005-08-18 5:19 ` Nathaniel Gray
2005-08-18 3:57 ` [Caml-list] Cost of register_global_root (was: Stopping a value from getting GC'd) Markus Mottl
2005-08-18 17:13 ` skaller [this message]
2005-08-18 10:51 ` Richard Jones
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=1124385201.8402.10.camel@localhost.localdomain \
--to=skaller@users.sourceforge.net \
--cc=caml-list@inria.fr \
--cc=markus.mottl@gmail.com \
--cc=n8gray@gmail.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