From: "Jon Harrop" <jon@ffconsultancy.com>
To: <caml-list@inria.fr>
Subject: RE: [Caml-list] Current state of threading parallelism?
Date: Sun, 6 Oct 2013 00:28:41 +0100 [thread overview]
Message-ID: <012f01cec222$a188b250$e49a16f0$@ffconsultancy.com> (raw)
In-Reply-To: <20131005022537.20edf93e@narfi.yggdrasil.draxit.de>
Francis Dupont wrote:
> Note this was the way followed by Python too for the same reasons
But not by JVM- and CLR-based languages like Java, Scala, C# and F#.
> Well, there are certain problems that can be largely parallelized
> in a way that performance scales well with the number of cores.
All problems can be parallelized such that performance scales well with the
number of cores. Just add redundant parallel computation of the Mandelbrot
set between each line of code. Consequently, it is important not to consider
scalability alone.
Cheers,
Jon.
prev parent reply other threads:[~2013-10-05 23:28 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
2013-10-05 3:57 ` Francois Berenger
2013-10-05 23:28 ` Jon Harrop [this message]
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='012f01cec222$a188b250$e49a16f0$@ffconsultancy.com' \
--to=jon@ffconsultancy.com \
--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