From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Original-To: caml-list@sympa.inria.fr Delivered-To: caml-list@sympa.inria.fr Received: from mail2-relais-roc.national.inria.fr (mail2-relais-roc.national.inria.fr [192.134.164.83]) by sympa.inria.fr (Postfix) with ESMTPS id 3F9B27EE4B for ; Sun, 6 Oct 2013 01:28:38 +0200 (CEST) Received-SPF: None (mail2-smtp-roc.national.inria.fr: no sender authenticity information available from domain of jon@ffconsultancy.com) identity=pra; client-ip=84.93.230.250; receiver=mail2-smtp-roc.national.inria.fr; envelope-from="jon@ffconsultancy.com"; x-sender="jon@ffconsultancy.com"; x-conformance=sidf_compatible Received-SPF: None (mail2-smtp-roc.national.inria.fr: no sender authenticity information available from domain of jon@ffconsultancy.com) identity=mailfrom; client-ip=84.93.230.250; receiver=mail2-smtp-roc.national.inria.fr; envelope-from="jon@ffconsultancy.com"; x-sender="jon@ffconsultancy.com"; x-conformance=sidf_compatible Received-SPF: None (mail2-smtp-roc.national.inria.fr: no sender authenticity information available from domain of postmaster@avasout05.plus.net) identity=helo; client-ip=84.93.230.250; receiver=mail2-smtp-roc.national.inria.fr; envelope-from="jon@ffconsultancy.com"; x-sender="postmaster@avasout05.plus.net"; x-conformance=sidf_compatible X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: AtcCAJSfUFJUXeb6nGdsb2JhbABZxRoEAoEYFg4BAQEBAQYNCQkUKIIlAQEEAQgCMEQIAwIJEAguGSMbAgQeBYdwCrt9jkWBExaEDQOPFIROmUQ X-IPAS-Result: AtcCAJSfUFJUXeb6nGdsb2JhbABZxRoEAoEYFg4BAQEBAQYNCQkUKIIlAQEEAQgCMEQIAwIJEAguGSMbAgQeBYdwCrt9jkWBExaEDQOPFIROmUQ X-IronPort-AV: E=Sophos;i="4.90,1040,1371074400"; d="scan'208";a="35725168" Received: from avasout05.plus.net ([84.93.230.250]) by mail2-smtp-roc.national.inria.fr with ESMTP; 06 Oct 2013 01:28:36 +0200 Received: from XPS ([87.115.139.190]) by avasout05 with smtp id ZbUb1m00246g2nr01bUcko; Sun, 06 Oct 2013 00:28:37 +0100 X-CM-Score: 0.00 X-CNFS-Analysis: v=2.1 cv=e+U/F8Z/ c=1 sm=1 tr=0 a=Fu7Kr69cXoyCR3DArX6Bzg==:117 a=Fu7Kr69cXoyCR3DArX6Bzg==:17 a=0Bzu9jTXAAAA:8 a=nWtk2VG-DNkA:10 a=Xub9RBUEA-sA:10 a=Kvk-SOs2Z7YA:10 a=kj9zAlcOel0A:10 a=r2vSxAw-AAAA:8 a=c3j_vBB6whIA:10 a=p0kqXZs-uwOZm1eO3CoA:9 a=GkAgvmptE5WTppBl:21 a=5gbq0oWLdJbzUvO6:21 a=CjuIK1q_8ugA:10 X-AUTH: jdh302:2500 Reply-To: From: "Jon Harrop" To: References: <20131004014649.2b4e7750@narfi.yggdrasil.draxit.de> <201310041544.r94FiR1h085910@givry.fdupont.fr> <20131005022537.20edf93e@narfi.yggdrasil.draxit.de> In-Reply-To: <20131005022537.20edf93e@narfi.yggdrasil.draxit.de> Date: Sun, 6 Oct 2013 00:28:41 +0100 Organization: Flying Frog Consultancy Ltd. Message-ID: <012f01cec222$a188b250$e49a16f0$@ffconsultancy.com> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Mailer: Microsoft Outlook 14.0 Thread-Index: AQHSlGApRAWHEiS7i8wLb5ELUUUx9wGzJNSjAkl5rdiZvzPQQA== Content-Language: en-gb Subject: RE: [Caml-list] Current state of threading parallelism? 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.