caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: oliver <oliver@first.in-berlin.de>
To: Thomas Braibant <thomas.braibant@gmail.com>
Cc: caml-list@inria.fr
Subject: Re: [Caml-list] Distributed computing libraries
Date: Wed, 6 Jun 2012 19:31:00 +0200	[thread overview]
Message-ID: <20120606173100.GB1824@siouxsie> (raw)
In-Reply-To: <CAHR=VkxRi3G3mtgCmWqByGirJZNjM6vv6y26RKmUsj_wXmnJ_g@mail.gmail.com>

On Wed, Jun 06, 2012 at 12:53:07PM -0400, Thomas Braibant wrote:
> 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/
[...]

  - CamlP3l http://camlp3l.inria.fr/eng.htm


[...]
> 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)?
[...]

Yes this would be fine.
And maybe "someone" could also mean some people...
...maybe there are people out there, that now one or two of them well,
and other of these libs not or not well.

...so that the information can be gathered by a lot of people.

But it would be fine to have some criteria for classifying.

For example:

  - one / multicore
  - local machine / distributed via net
  - threads / processes
  - just library calls, language extension, or seperate language 
  - toplevel-runtime / byte code / native-code
  - necessity of code rewrite for local and remote/distributive stuff,
     or possibility of transparent usage
  - ...


Ciao,
   Oliver

  reply	other threads:[~2012-06-06 17:31 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 [this message]
2012-06-06 17:34   ` Vincent Aravantinos
2012-06-06 18:01 ` AW: " Gerd Stolpmann
2012-06-06 18:16   ` 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=20120606173100.GB1824@siouxsie \
    --to=oliver@first.in-berlin.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;
as well as URLs for NNTP newsgroup(s).