Mailing list for all users of the OCaml language and system.
 help / color / mirror / Atom feed
From: Jon Harrop <jon@ffconsultancy.com>
To: caml-list@yquem.inria.fr
Subject: Re: [Caml-list] The state of ML: multi-threaded, saved state and support platforms
Date: Thu, 11 Jun 2009 22:46:48 +0100	[thread overview]
Message-ID: <200906112246.48317.jon@ffconsultancy.com> (raw)
In-Reply-To: <20090611154910.GA27827@annexia.org>

On Thursday 11 June 2009 16:49:10 Richard Jones wrote:
> which will work better on new multicore machines which are all NUMA
> nowadays, 

Spawning parallel work items is 30,000x faster in F# using the TPL than in 
OCaml using fork. Passing data is asymptotically faster in F# using the TPL 
than in OCaml using MPI. Cilk is much faster still.

In other words, F# can do 60MFLOPS of computation in the time it takes OCaml 
to fork a single process.

Suffice to say, there is no way any approach currently available in 
OCaml "will work better on new multicore machines".

> and in any case is simpler to program

On the contrary, OCaml is a *lot* harder to program because it introduces 
additional complexity. Specifically, communication is now O(n) instead of 
O(1), including gathering the results of parallel computations. There are 
workarounds but they require manual memory management which is even more 
unnecessary complexity.

-- 
Dr Jon Harrop, Flying Frog Consultancy Ltd.
http://www.ffconsultancy.com/?e


  parent reply	other threads:[~2009-06-11 21:41 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-06-11 14:04 Lucas Dixon
2009-06-11 15:49 ` [Caml-list] " Richard Jones
2009-06-11 21:44   ` Lucas Dixon
2009-06-11 22:10     ` Richard Jones
2009-06-11 22:53     ` Sylvain Le Gall
2009-06-12  0:28     ` [Caml-list] " Jon Harrop
2009-06-12  8:24       ` Daniel Bünzli
2009-06-11 21:46   ` Jon Harrop [this message]
2009-06-11 16:55 ` Florian Weimer
2009-06-11 21:01   ` Lucas Dixon

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=200906112246.48317.jon@ffconsultancy.com \
    --to=jon@ffconsultancy.com \
    --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