From: Philippe Wang <mail@philippewang.info>
To: Wolfgang Draxinger <wdraxinger.maillist@draxit.de>
Cc: OCaml Mailing List <caml-list@inria.fr>,
Francis Dupont <Francis.Dupont@fdupont.fr>,
Mathias Bourgoin <mathias.bourgoin@lip6.fr>
Subject: Re: [Caml-list] Current state of threading parallelism?
Date: Sat, 5 Oct 2013 02:25:13 +0100 [thread overview]
Message-ID: <CAAFfW_o7prPb_CibBFXqcRDwb==vdMRJDweP84po=gXpB8Y3zg@mail.gmail.com> (raw)
In-Reply-To: <20131005022537.20edf93e@narfi.yggdrasil.draxit.de>
On Sat, Oct 5, 2013 at 1:25 AM, Wolfgang Draxinger
<wdraxinger.maillist@draxit.de> wrote:
> On Fri, 04 Oct 2013 17:44:27 +0200
> Francis Dupont <Francis.Dupont@fdupont.fr> wrote:
>
>> => yes, this is the official way (no shared memory, no fine grain
>> locking, etc). Note this was the way followed by Python too for
>> the same reasons (to make the intepreter multi-threaded was considered
>> as too hard for the expected best result, i.e., ~4 time maximum speed
>> up).
>
> Well, there are certain problems that can be largely parallelized in a
> way that performance scales well with the number of cores. Those
> problems usually also perform in constant memory (of course this is all
> mutable state then, so not really pure). I'm thinking of problems that
> could be put as well on GPUs here, like signal decomposition, error
> diffusion models, stuff like that.
You might want to get a look at SPOC:
http://www.algo-prog.info/spoc/
N.B. It's even in OPAM!
--
Philippe Wang
mail@philippewang.info
next prev parent reply other threads:[~2013-10-05 1:25 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-03 23:46 Wolfgang Draxinger
2013-10-03 23:50 ` Francois Berenger
2013-10-04 15:44 ` Francis Dupont
2013-10-05 0:25 ` Wolfgang Draxinger
2013-10-05 1:25 ` Philippe Wang [this message]
2013-10-05 3:57 ` Francois Berenger
2013-10-05 23:28 ` Jon Harrop
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='CAAFfW_o7prPb_CibBFXqcRDwb==vdMRJDweP84po=gXpB8Y3zg@mail.gmail.com' \
--to=mail@philippewang.info \
--cc=Francis.Dupont@fdupont.fr \
--cc=caml-list@inria.fr \
--cc=mathias.bourgoin@lip6.fr \
--cc=wdraxinger.maillist@draxit.de \
/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).