From: Christophe Raffalli <christophe.raffalli@univ-savoie.fr>
To: skaller@users.sourceforge.net
Cc: Jacques Garrigue <garrigue@kurims.kyoto-u.ac.jp>,
Christoph.Bauer@lms-gmbh.de, caml-list <caml-list@inria.fr>
Subject: Re: AW: [Caml-list] The tag bit
Date: Fri, 13 Aug 2004 17:44:17 +0200 [thread overview]
Message-ID: <411CE1D1.8070304@univ-savoie.fr> (raw)
In-Reply-To: <1092407293.29139.219.camel@pelican.wigram>
skaller wrote:
> On Fri, 2004-08-13 at 22:58, Christophe Raffalli wrote:
>
>
>>Does anyone have a comparison between two identical GC except one
>>should have a tag bit and the other be conservative ?
>
>
> The Boehm collector is quite efficient: if you compare it
> to hand written encodings such as reference counting
> for example.
>
> The main problem with it is that it has to 'stop the world'
> whilst it is doing its thing, and so isn't useful for
> real time applications such as a game where you can easily
> pay 20% of all CPU for the GC -- but you simply can't freeze
> up the game for 10 seconds every few minutes.
>
> The Ocaml generational collector is likely to be much better
> at this -- some of the workload is spread over time, and
> the remaining major collection when needed will also be
> faster, and can be called manually at appropriate points.
>
> A second point is -- Boehm cannot defragment memory.
> Ocaml can (although the compaction is 'world stop').
>
> So .. i don't think the 'overall CPU use' of the two collector
> kinds is actually what you need to compare: the real time
> performance and/or ability to operate with C/C++ code
> are the likely issues.
>
>
It is not true, on some configuration (including intel I think) Boehm's
GC can be incremental. At least the documentation say so.
--
Christophe Raffalli
Université de Savoie
Batiment Le Chablais, bureau 21
73376 Le Bourget-du-Lac Cedex
tél: (33) 4 79 75 81 03
fax: (33) 4 79 75 87 42
mail: Christophe.Raffalli@univ-savoie.fr
www: http://www.lama.univ-savoie.fr/~RAFFALLI
---------------------------------------------
IMPORTANT: this mail is signed using PGP/MIME
At least Enigmail/Mozilla, mutt or evolution
can check this signature
---------------------------------------------
-------------------
To unsubscribe, mail caml-list-request@inria.fr Archives: http://caml.inria.fr
Bug reports: http://caml.inria.fr/bin/caml-bugs FAQ: http://caml.inria.fr/FAQ/
Beginner's list: http://groups.yahoo.com/group/ocaml_beginners
next prev parent reply other threads:[~2004-08-13 15:44 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-12 15:22 Bauer, Christoph
2004-08-13 3:53 ` Jacques Garrigue
2004-08-13 12:58 ` Christophe Raffalli
2004-08-13 13:14 ` [Caml-list] Other GC in ML family ? Diego Olivier Fernandez Pons
2004-08-13 13:24 ` AW: [Caml-list] The tag bit Andreas Rossberg
2004-08-13 14:32 ` T. Kurt Bond
2004-08-13 14:41 ` AW: [Caml-list] Conservative GC T. Kurt Bond
2004-08-13 16:14 ` AW: [Caml-list] The tag bit Ville-Pertti Keinonen
2004-08-13 14:28 ` skaller
2004-08-13 15:44 ` Christophe Raffalli [this message]
2004-08-13 15:40 ` Brian Hurt
2004-08-13 13:43 Ennals, Robert
2004-08-13 14:58 Ennals, Robert
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=411CE1D1.8070304@univ-savoie.fr \
--to=christophe.raffalli@univ-savoie.fr \
--cc=Christoph.Bauer@lms-gmbh.de \
--cc=caml-list@inria.fr \
--cc=garrigue@kurims.kyoto-u.ac.jp \
--cc=skaller@users.sourceforge.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