From: "Berke Durak" <berke.durak@gmail.com>
To: "Yaron Minsky" <yminsky@janestcapital.com>
Cc: "Dario Teixeira" <darioteixeira@yahoo.com>,
"Caml List" <caml-list@inria.fr>
Subject: Re: [Caml-list] OCaml Summer Project decisions are in
Date: Sat, 19 Apr 2008 10:46:53 +0200 [thread overview]
Message-ID: <b903a8570804190146g35312edbid0bb8e5e8e28dd01@mail.gmail.com> (raw)
In-Reply-To: <1208546581.16295.108.camel@nyc-qws-018.delacy.com>
[-- Attachment #1: Type: text/plain, Size: 1157 bytes --]
The concurrent GC is a great idea. A few interrogations.
- How "stoppy" would a stop-the-world parallel GC be in practice? The more
parallelism
you have, the more work is done, the higher the frequency of a major
collection.
- Would major allocations be serialized? What about other serialization
points?
- I'm afraid true concurrency will introduce an awful lot of bugs in native
bindings. Thread-unsafe libraries will have to be replaced (Str, etc.)
Also what would be the CPU
and memory costs? Don't concurrent GCs require extra colors?
- In case of performance impacts, will the old single-threaded mode still be
available?
The argument that "you'll get the same old perfomance if you run it in
single-threaded mode"
is not valid IMHO. Many people will use a thread here or there and then you
won't realistically be able to run in single-threaded mode.
But then we can't pretend multi-core doesn't exist. A suggestion: making
the parallel GC available only on 64-bit seems a reasonable restriction (if
that's ever needed.)
Also Damien Doligez (in addition to Xavier Leroy) certainly have nice things
to say about all this.
--
Berke Durak
[-- Attachment #2: Type: text/html, Size: 1315 bytes --]
next prev parent reply other threads:[~2008-04-19 8:46 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-18 14:51 Yaron Minsky
2008-04-18 15:46 ` [Caml-list] " Jon Harrop
2008-04-18 16:42 ` Dario Teixeira
2008-04-18 19:23 ` Yaron Minsky
2008-04-19 8:46 ` Berke Durak [this message]
2008-04-19 14:21 ` Benjamin Canou
2008-04-20 16:12 ` Xavier Leroy
2008-04-21 9:24 ` Berke Durak
2008-04-21 11:17 ` Jon Harrop
2008-04-19 11:29 ` Francois Pottier
2008-04-19 15:11 ` Dario Teixeira
2008-04-19 13:38 ` Sylvain Le Gall
2008-04-20 20:06 ` [Caml-list] " Florian Hars
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=b903a8570804190146g35312edbid0bb8e5e8e28dd01@mail.gmail.com \
--to=berke.durak@gmail.com \
--cc=caml-list@inria.fr \
--cc=darioteixeira@yahoo.com \
--cc=yminsky@janestcapital.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