From: Jonathan Bryant <jtbryant@valdosta.edu>
To: caml-list@yquem.inria.fr
Subject: Re: [Caml-list] Faking concurrency using Unix forks and pipes (ray tracing results)
Date: Mon, 4 Jun 2007 11:33:26 -0400 [thread overview]
Message-ID: <67BC38F1-55DA-46F6-B35E-E728F7B1154B@valdosta.edu> (raw)
In-Reply-To: <200706041156.16521.jon@ffconsultancy.com>
On Jun 4, 2007, at 6:56 AM, Jon Harrop wrote:
>
> When you apply this map to an array, a new process is forked for
> each element.
> As forking is time consuming, you should only apply this to short
> arrays.
It might be worth your while to implement a process pool. I said
before that I fork of one base process from which to fork the others,
and it's not possible to make that process just a controller for a
pool of waiting processes.
--Jonathan
next prev parent reply other threads:[~2007-06-04 15:34 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-04 10:56 Jon Harrop
2007-06-04 15:33 ` Jonathan Bryant [this message]
2007-06-04 15:39 ` [Caml-list] " Jonathan Bryant
[not found] ` <9b415f950706040850v586a285ax1448d23c0c78a375@mail.gmail.com>
2007-06-04 16:13 ` Jonathan Bryant
[not found] ` <9b415f950706040933r22e1560fhc088368ccb8444fa@mail.gmail.com>
2007-06-04 16:53 ` Jonathan Bryant
2007-06-04 18:00 ` Brian Hurt
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=67BC38F1-55DA-46F6-B35E-E728F7B1154B@valdosta.edu \
--to=jtbryant@valdosta.edu \
--cc=caml-list@yquem.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).