From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: 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 A1CC6820A1 for ; Wed, 11 Sep 2013 15:00:20 +0200 (CEST) Received-SPF: None (mail2-smtp-roc.national.inria.fr: no sender authenticity information available from domain of berenger@riken.jp) identity=pra; client-ip=134.160.33.161; receiver=mail2-smtp-roc.national.inria.fr; envelope-from="berenger@riken.jp"; x-sender="berenger@riken.jp"; x-conformance=sidf_compatible Received-SPF: Pass (mail2-smtp-roc.national.inria.fr: domain of berenger@riken.jp designates 134.160.33.161 as permitted sender) identity=mailfrom; client-ip=134.160.33.161; receiver=mail2-smtp-roc.national.inria.fr; envelope-from="berenger@riken.jp"; x-sender="berenger@riken.jp"; x-conformance=sidf_compatible; x-record-type="v=spf1" Received-SPF: Pass (mail2-smtp-roc.national.inria.fr: domain of postmaster@postman.riken.jp designates 134.160.33.161 as permitted sender) identity=helo; client-ip=134.160.33.161; receiver=mail2-smtp-roc.national.inria.fr; envelope-from="berenger@riken.jp"; x-sender="postmaster@postman.riken.jp"; x-conformance=sidf_compatible; x-record-type="v=spf1" X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: Ap8BAPtnMFKGoCGhnGdsb2JhbABbxnGBMg4BAQEBAQgLCQkUKIIlAQEFODQKEwsYCSUPAkYTBgIBAYd9AcRdjhuBVhaEBwOJNY5ElSM X-IPAS-Result: Ap8BAPtnMFKGoCGhnGdsb2JhbABbxnGBMg4BAQEBAQgLCQkUKIIlAQEFODQKEwsYCSUPAkYTBgIBAYd9AcRdjhuBVhaEBwOJNY5ElSM X-IronPort-AV: E=Sophos;i="4.90,884,1371074400"; d="scan'208";a="32433049" Received: from postman1.riken.jp (HELO postman.riken.jp) ([134.160.33.161]) by mail2-smtp-roc.national.inria.fr with ESMTP; 11 Sep 2013 15:00:18 +0200 Received: from postman.riken.jp (postman1.riken.jp [127.0.0.1]) by postman.riken.jp (Postfix) with SMTP id 6548D32C014A for ; Wed, 11 Sep 2013 22:00:15 +0900 (JST) Received: from fbrs-iMac.local (usr013.bb802-01.ual.im.wakwak.ne.jp [219.121.104.207]) by postman.riken.jp (Postfix) with ESMTPA id 0330B32A0085 for ; Wed, 11 Sep 2013 22:00:14 +0900 (JST) Message-ID: <5230695E.20100@riken.jp> Date: Wed, 11 Sep 2013 22:00:14 +0900 From: Francois Berenger User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:17.0) Gecko/20130801 Thunderbird/17.0.8 MIME-Version: 1.0 To: caml-list@inria.fr References: <5229DEF9.7040706@inria.fr> <5229F284.5050806@inria.fr> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-PMX-Version: 6.0.0.2142326, Antispam-Engine: 2.7.2.2107409, Antispam-Data: 2013.9.11.125114 Subject: Re: [Caml-list] Accelerating compilation On 9/7/13 5:51 AM, Fabrice Le Fessant wrote: > On Fri, Sep 6, 2013 at 5:20 PM, Romain Bardou wrote: >>>> 3) Parallel compilation in Ocamlbuild >>>> >>>> Of course it would help but it is not easy to implement so I'm just >>>> putting it there to be exhaustive. >>> >>> I'm not sure what you are referring to, OCamlBuild does already >>> support parallel builds. >> >> Does it? I actually thought the -j option was ignored. >> >> I just did a quick test and I gain about 5 seconds with -j on a 1min15 >> build (I had cleaned, recompiled and recleaned before so that caching by >> the file system would not impact the result too much), so it does seem >> to be a *little* faster :) > > FWIW, I recently compiled Merlin with both ocamlbuild and ocp-build, > on a quad-core with "-j 10" for both (the link to the ocp-build > description file is in the latest OCamlPro's report), ocamlbuild needs > 13s where ocp-build only needs 4s to compile everything. This morning, I played with a Makefile and ocamlbuild to build batteries-included from a clean source tree. The Makefile was provided by Cedric Cellier. Here follows the wallclock times to build on my eight cores machine. #You can plot them like this: cat < make_Vs_ocamlbuild.data #nprocs Makefile ocamlbuild 1 14.52 21.43 2 6.84 17.57 3 4.95 16.44 4 4.18 15.95 5 3.70 15.67 6 3.36 15.62 7 3.12 15.54 8 3.03 15.292 EOF gnuplot -persist <