From: Nathaniel Gray <n8gray@gmail.com>
To: Alain Frisch <Alain.Frisch@inria.fr>
Cc: Bardur Arantsson <spam@scientician.net>, caml-list@inria.fr
Subject: Re: [Caml-list] Cost of register_global_root
Date: Wed, 17 Aug 2005 22:19:09 -0700 [thread overview]
Message-ID: <aee06c9e05081722197ea9f7a7@mail.gmail.com> (raw)
In-Reply-To: <4303F52B.8010400@inria.fr>
On 8/17/05, Alain Frisch <Alain.Frisch@inria.fr> wrote:
> Nathaniel Gray 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?
>
> The runtime system stores the global roots in a skip list. One should
> expect probabilistic O(log n) complexity with a small constant for each
> insertion and deletion, where n is the number of already registered
> global roots.
Sounds reasonable.
> Another option is to manage the roots yourself (e.g. you put them in an
> array and store indexes into this array in your custom data structure).
That's exactly what I was planning, but I wasn't entirely sure it was
actually necessary.
> This might be necessary if the custom blocks are under the control of
> another memory management system which can moves blocks around.
Thanks,
-n8
--
>>>-- Nathaniel Gray -- Caltech Computer Science ------>
>>>-- Mojave Project -- http://mojave.cs.caltech.edu -->
next prev parent reply other threads:[~2005-08-18 5:19 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 [this message]
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
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=aee06c9e05081722197ea9f7a7@mail.gmail.com \
--to=n8gray@gmail.com \
--cc=Alain.Frisch@inria.fr \
--cc=caml-list@inria.fr \
--cc=spam@scientician.net \
/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