From: Francois Berenger <berenger@riken.jp>
To: caml-list@inria.fr
Subject: Re: [Caml-list] Distributed computing libraries
Date: Fri, 08 Jun 2012 15:36:29 +0900 [thread overview]
Message-ID: <4FD19D6D.4000108@riken.jp> (raw)
In-Reply-To: <CAHR=Vkxy0k-SRJYixWpxpDMjpp+yCBJNhY013UbHMgQQT_gRvA@mail.gmail.com>
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.
>
> 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.
Roberto Di Cosmo just created a home page:
http://www.dicosmo.org/code/parmap/
The ocamldoc-generated pages are here:
http://www.dicosmo.org/code/parmap/doc/Parmap.html
Regards,
F.
> 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.
>
> 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.
>
> 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)?
>
> Maybe that I should add some criteria to Oliver's list:
> - active / inactive
> - used in the wild
> - documentation (API, manual)
> - examples / tutorials
>
> With best regards,
> Thomas
>
next prev parent reply other threads:[~2012-06-08 6:36 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
2012-06-08 6:36 ` Francois Berenger [this message]
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=4FD19D6D.4000108@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