caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: Jerome Vouillon <vouillon@pps.jussieu.fr>
To: Martin Jambon <martin.jambon@ens-lyon.org>
Cc: OCaml Mailing List <caml-list@inria.fr>
Subject: Re: [Caml-list] Nproc: process pools for OCaml (request for suggestions)
Date: Wed, 30 Nov 2011 10:35:57 +0100	[thread overview]
Message-ID: <20111130093557.GA19471@pps.jussieu.fr> (raw)
In-Reply-To: <4ED59AF6.1030506@ens-lyon.org>

Hi,

On Tue, Nov 29, 2011 at 06:54:46PM -0800, Martin Jambon wrote:
> I would like to publicize Nproc, which is an implementation of process
> pools for OCaml based on fork, pipes, Marshal and Lwt:
> 
>   https://github.com/MyLifeLabs/nproc
> 
> Using Nproc involves:
> 
> 1. Creating a pool of N processes, N being chosen by the user.
> 2. Running tasks:
>   a. Submitting a task (f, x) of any type.
>   b. Defining what to do when the result becomes available.

Marco Danelutto and Roberto Di Cosmo have written a small library to
perform parallel maps and folds on multi-core machines. This is
complementary to your library. You should look at the implementation:
communication is performed by marshalling to a shared memory area for
better performances, and pipes are used only for synchronization.

     https://gitorious.org/parmap/


I have also written a more low-level library, where you can control
which process runs each task. This is useful when the processes have
to work with a lot of data that you don't want to duplicate. You can
get the code with the following command:

     darcs clone http://www.pps.jussieu.fr/~vouillon/coinst/darcs/dev/

The file of interest is task.ml.

-- Jerome

  reply	other threads:[~2011-11-30  9:37 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-11-30  2:54 Martin Jambon
2011-11-30  9:35 ` Jerome Vouillon [this message]
2011-11-30 21:32   ` Martin Jambon

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=20111130093557.GA19471@pps.jussieu.fr \
    --to=vouillon@pps.jussieu.fr \
    --cc=caml-list@inria.fr \
    --cc=martin.jambon@ens-lyon.org \
    /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).