From: Gerd Stolpmann <info@gerd-stolpmann.de>
To: Thomas Braibant <thomas.braibant@gmail.com>
Cc: caml-list@inria.fr
Subject: AW: [Caml-list] Distributed computing libraries
Date: Wed, 06 Jun 2012 20:01:32 +0200 [thread overview]
Message-ID: <1339005692.4950.2@samsung> (raw)
In-Reply-To: <CAHR=VkxRi3G3mtgCmWqByGirJZNjM6vv6y26RKmUsj_wXmnJ_g@mail.gmail.com> (from thomas.braibant@gmail.com on Wed Jun 6 18:53:07 2012)
Am 06.06.2012 18:53:07 schrieb(en) Thomas Braibant:
> Hi list,
>
> There exists several different "distributed computing libraries" in
> OCaml:
>
> - Functory http://functory.lri.fr/
> - JoCaml http://jocaml.inria.fr/ (not really a library, though)
> - Nproc https://github.com/MyLifeLabs/nproc
> - OCaml for multicore http://www.algo-prog.info/ocmc/web/ (not a
> library either)
> - Parmap https://gitorious.org/parmap/parmap
> - Plasma Map/Reduce http://plasma.camlcity.org/plasma/
>
These are very different pieces of software, because they tackle
problems at various abstraction levels. ocmc is the most level-level
here, as it "only" tries to improve the runtime so that threads can be
run in parallel on multiple cores. That's it, there is no additional
abstraction on top of the standard threading API - no distribution, no
computing.
JoCaml uses the normal multi-threading in the runtime, but integrates
it differently into the language. So, it adds abstraction, but you are
still limited to a single core.
So far I know, all the other libraries base on multi-processing to run
programs on multiple cores. Plasma is the only one with true
distribution capabiltiies beyond a single computer, but the price is
that you must use the map/reduce scheme, whereas functory or parmap
leave you more freedom. However, all multi-processing approaches share
the property that the data flow is limited by process boundaries
(unless you go really low-level and also take Netmulticore into
consideration (part of Ocamlnet), which uses shared memory to overcome
these limitations).
I don't know what you are exactly looking for. Knowing the problem it
would be easier to recommend something.
Gerd
> And I am pretty sure that this list is not exhaustive, looking at
> http://caml.inria.fr/cgi-bin/hump.en.cgi?sort=0&browse=77
>
> Maybe it would be interesting for the community if someone could sum
> up the pros and cons of each of this "libraries", and maybe give some
> information about their status (still in development, mature, etc)?
>
> With best regards,
> Thomas Braibant
>
> --
> Caml-list mailing list. Subscription management and archives:
> https://sympa-roc.inria.fr/wws/info/caml-list
> Beginner's list: http://groups.yahoo.com/group/ocaml_beginners
> Bug reports: http://caml.inria.fr/bin/caml-bugs
>
>
>
--
------------------------------------------------------------
Gerd Stolpmann, Darmstadt, Germany gerd@gerd-stolpmann.de
Creator of GODI and camlcity.org.
Contact details: http://www.camlcity.org/contact.html
Company homepage: http://www.gerd-stolpmann.de
------------------------------------------------------------
next prev parent reply other threads:[~2012-06-06 18:01 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-06 16:53 Thomas Braibant
2012-06-06 17:31 ` oliver
2012-06-06 17:34 ` Vincent Aravantinos
2012-06-06 18:01 ` Gerd Stolpmann [this message]
2012-06-06 18:16 ` AW: " Edgar Friendly
2012-06-06 18:18 ` oliver
2012-06-06 18:35 ` AW: " Gerd Stolpmann
2012-06-06 18:44 ` Edgar Friendly
2012-06-06 20:52 ` Thomas Braibant
2012-06-07 1:34 ` Francois Berenger
2012-06-07 15:44 ` Thomas Braibant
2012-06-08 0:53 ` Francois Berenger
2012-06-08 6:36 ` Francois Berenger
2012-06-06 20:24 ` Roberto Di Cosmo
2012-06-06 20:43 ` Thomas Braibant
2012-06-07 1:48 ` [Caml-list] OCaml package managers Francois Berenger
2012-06-06 22:23 ` [Caml-list] Distributed computing libraries Ashish Agarwal
2012-06-08 6:55 ` Roberto Di Cosmo
2012-06-11 14:48 ` Ashish Agarwal
2012-06-08 8:58 ` jean-marc alliot
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=1339005692.4950.2@samsung \
--to=info@gerd-stolpmann.de \
--cc=caml-list@inria.fr \
--cc=thomas.braibant@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