caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: Thomas Braibant <thomas.braibant@gmail.com>
To: Gerd Stolpmann <info@gerd-stolpmann.de>
Cc: caml-list@inria.fr
Subject: Re: [Caml-list] Distributed computing libraries
Date: Wed, 6 Jun 2012 16:52:08 -0400	[thread overview]
Message-ID: <CAHR=VkzFnTY_7=5esH-L5wZ-fGLT7KkwuVi-ZbLPev+Uvj1L-A@mail.gmail.com> (raw)
In-Reply-To: <1339005692.4950.2@samsung>

> 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.

Thanks a lot for this answer.

As I said in another email, I do not have a problem to solve right
now. But, I was tickled by the Parmap announce, and I wondered how it
fared with the other related systems I knew about. (Yet, I reckon that
I should have made the question more precise, with a detailed lists of
criteria, akin to what Oliver suggested.)

In my mind, asking on the list was the best way to make a good summary
of the current situation on this front. (But I am afraid I do not know
the best place to make public this kind of summaries.)

  parent reply	other threads:[~2012-06-06 20:52 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 ` 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 [this message]
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='CAHR=VkzFnTY_7=5esH-L5wZ-fGLT7KkwuVi-ZbLPev+Uvj1L-A@mail.gmail.com' \
    --to=thomas.braibant@gmail.com \
    --cc=caml-list@inria.fr \
    --cc=info@gerd-stolpmann.de \
    /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).