caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: Francois Berenger <berenger@riken.jp>
To: caml-list <caml-list@inria.fr>
Subject: Re: [Caml-list] Distributed computing libraries
Date: Fri, 08 Jun 2012 09:53:55 +0900	[thread overview]
Message-ID: <4FD14D23.5040906@riken.jp> (raw)
In-Reply-To: <CAHR=Vkxy0k-SRJYixWpxpDMjpp+yCBJNhY013UbHMgQQT_gRvA@mail.gmail.com>

Hello,

On 06/08/2012 12:44 AM, Thomas Braibant wrote:
>> Don't hesitate, jump on it, that's really a nice technology.
>> The "minimal disruption" concept is quite interesting.
>> For example, if your List.iter is changed to a Parmap.pariter,
>> the parallelization of this portion of the code is done.
>>
>> It's quite comfortable to develop and debug in single core mode (List.iter)
>> and switch to the // version only once you're happy with
>> the sequential one.
>
> I see. However, looking at, e.g., Functory,
> http://www.lri.fr/~filliatr/functory/doc/Functory.Cores.html it seems
> that I can use it in the same fashion (Using Functory.Cores.map
> instead of List.map) and that I can debug my code using
> Functory.Sequential.map.

Functory can distribute computations while parmap can only parallelize 
them on your local machine.
I'm pretty sure that parmap is faster at doing what they can be compared 
on because it has specialized optimizations that you cannot use if your 
data has to be distributed over the network.

The last time I looked at Functory:
- Functory had several not tail recursive functions and blew my stack
   (it was about one year ago, maybe things have changed)
- not any mailing list for functory
- while parmap has:
   parmap-devel <parmap-devel@inria.fr> and
   parmap-users <parmap-users@inria.fr>
- no GODI package for functory
- parmap has a GODI package (thanks to Jerome
   Maloberti) and maybe very soon an oasis one

> So this does not really discriminate between the two libraries. Note,
> however, that I cannot find Parmap's API described on line (using
> ocamldoc). Right now, it seems that I have to download it, to generate
> the doc.

At least there is a doc and you even managed to generate it.
('make doc' in a parmap checkout).
Maybe the doc will be online soon, who knows. ;)

> Note that Gerd's Plasma Map/Reduce has a nice and comprehensive
> documentation available, but, being more ambitious maybe, it is harder
> for a beginner to find his/her way in: the entry cost is higher.

It's also for distributed computing, parmap is for local parallelization.

> By comparison, JOcaml's manual is written in a quasi-tutorial fashion
> ( http://jocaml.inria.fr/doc/index.html ) which makes it more easy to
> start hacking stuff, even if the scope is a bit different.

I'm not sure it's standard OCaml code then.
At least with parmap and functory, they are just libraries that
you can plug into any plain vanilla OCaml source code.

> And what about CamlP3l? What is its status? Is it superseded by Parmap
> (the lists of authors of the two softwares have a non-empty
> intersection)?

I don't think it's just a library too.
Some more knowledgeable people may answer you on these.

Regards,
F.

  reply	other threads:[~2012-06-08  0:54 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
2012-06-07  1:34     ` Francois Berenger
2012-06-07 15:44       ` Thomas Braibant
2012-06-08  0:53         ` Francois Berenger [this message]
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=4FD14D23.5040906@riken.jp \
    --to=berenger@riken.jp \
    --cc=caml-list@inria.fr \
    /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).