From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Original-To: caml-list@sympa.inria.fr Delivered-To: caml-list@sympa.inria.fr Received: from mail4-relais-sop.national.inria.fr (mail4-relais-sop.national.inria.fr [192.134.164.105]) by sympa.inria.fr (Postfix) with ESMTPS id DBA347ED26 for ; Thu, 7 Jun 2012 17:44:39 +0200 (CEST) X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: AlABAD3L0E/RVdW2imdsb2JhbABFFrQDCCIBAQEKCQ0HEgYjghgBAQEDARICLAEbHQEDAQsGBQs7IgERAQUBHAY1h1oBAwYFC5o0CQOMIoJwhQMKGScNV4hxAQUMkR0DlR2BEoltgx4+hBs X-IronPort-AV: E=Sophos;i="4.75,731,1330902000"; d="scan'208";a="146936345" Received: from mail-yx0-f182.google.com ([209.85.213.182]) by mail4-smtp-sop.national.inria.fr with ESMTP/TLS/RC4-MD5; 07 Jun 2012 17:44:39 +0200 Received: by yenl8 with SMTP id l8so808149yen.27 for ; Thu, 07 Jun 2012 08:44:38 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type; bh=VJwh9bVBPuOsYJ3ZRDY8rPBL+UQV4cqPG4JVZKfT7sQ=; b=cf3dGnWG4hDXADwKWui+RymhOYuU3umUjmx7k919W2KPmTikj+EJVjf50RZYp0qQ1b MZrvmCoUIYFfehedtfJfzlHguKPEOXgKQafmbT0y7xG0fPNwysDvaLBhK1orxi8uX/oI uHTzY9Wa/piLXMh0mvFmbCIlsFA86KE/YRCjJb5yfPmMpr20AZn62Doteb9Mhtzi312n QfAEmX5AwEI815TWXwrizaDlz1DhoryJaw07vc6yPnFNAEBb49AWpSWU299rBIyHyxd0 L/ZeANDJb/Prp2xf2Mxdb9RwnlVL3CpRrxtlCXS9AqKXZ4zXlxKOadL6fKumQR1q3T4a /Xug== Received: by 10.60.2.3 with SMTP id 3mr2694809oeq.29.1339083878013; Thu, 07 Jun 2012 08:44:38 -0700 (PDT) MIME-Version: 1.0 Received: by 10.76.21.235 with HTTP; Thu, 7 Jun 2012 08:44:17 -0700 (PDT) In-Reply-To: <4FD0053B.5020600@riken.jp> References: <1339005692.4950.2@samsung> <4FD0053B.5020600@riken.jp> From: Thomas Braibant Date: Thu, 7 Jun 2012 11:44:17 -0400 Message-ID: To: Francois Berenger Cc: caml-list@inria.fr Content-Type: text/plain; charset=ISO-8859-1 Subject: Re: [Caml-list] Distributed computing libraries > 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. 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