From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail3-relais-sop.national.inria.fr (mail3-relais-sop.national.inria.fr [192.134.164.104]) by sympa.inria.fr (Postfix) with ESMTPS id A98EF7EE4B for ; Mon, 30 Sep 2013 11:19:29 +0200 (CEST) Received-SPF: None (mail3-smtp-sop.national.inria.fr: no sender authenticity information available from domain of berenger@riken.jp) identity=pra; client-ip=134.160.33.162; receiver=mail3-smtp-sop.national.inria.fr; envelope-from="berenger@riken.jp"; x-sender="berenger@riken.jp"; x-conformance=sidf_compatible Received-SPF: Pass (mail3-smtp-sop.national.inria.fr: domain of berenger@riken.jp designates 134.160.33.162 as permitted sender) identity=mailfrom; client-ip=134.160.33.162; receiver=mail3-smtp-sop.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 (mail3-smtp-sop.national.inria.fr: domain of postmaster@postman.riken.jp designates 134.160.33.162 as permitted sender) identity=helo; client-ip=134.160.33.162; receiver=mail3-smtp-sop.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: AnsBAGxBSVKGoCGinGdsb2JhbABagz/BTIE9DgEBAQEBCAsJCRQogiUBAQQBODMNEQsYCRYPCQMCAQIBRRMGAgEBh3wGvFqPWBaEDAOJN45IgS+FBI0sgU0 X-IPAS-Result: AnsBAGxBSVKGoCGinGdsb2JhbABagz/BTIE9DgEBAQEBCAsJCRQogiUBAQQBODMNEQsYCRYPCQMCAQIBRRMGAgEBh3wGvFqPWBaEDAOJN45IgS+FBI0sgU0 X-IronPort-AV: E=Sophos;i="4.90,1007,1371074400"; d="scan'208";a="28526532" Received: from postman2.riken.jp (HELO postman.riken.jp) ([134.160.33.162]) by mail3-smtp-sop.national.inria.fr with ESMTP; 30 Sep 2013 11:19:28 +0200 Received: from postman.riken.jp (postman2.riken.jp [127.0.0.1]) by postman.riken.jp (Postfix) with SMTP id 4BD2B1260628 for ; Mon, 30 Sep 2013 18:19:25 +0900 (JST) Received: from [172.27.98.103] (rikad98.riken.jp [134.160.214.98]) by postman.riken.jp (Postfix) with ESMTPA id 685701270051 for ; Mon, 30 Sep 2013 18:19:23 +0900 (JST) Message-ID: <524941F6.2010707@riken.jp> Date: Mon, 30 Sep 2013 18:18:46 +0900 From: Francois Berenger User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Thunderbird/24.0 MIME-Version: 1.0 To: caml-list@inria.fr References: <5229DEF9.7040706@inria.fr> <5229F284.5050806@inria.fr> <5249310F.7090108@riken.jp> 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.30.90617 Subject: Re: [Caml-list] from oasis to obuild (original subject was Re: Accelerating compilation) On 09/30/2013 06:00 PM, Fabrice Le Fessant wrote: > On Mon, Sep 30, 2013 at 10:07 AM, Francois Berenger wrote: >> # time ./build.sh >> real 0m9.397s >> >> Compile time after, with obuild: >> # obuild clean && time (obuild configure && obuild build -j 1) >> real 0m3.624s > > If you compile with "-j 1", where does the speed-up come from ? Good question that I will leave the experts to answer. > Is > Oasis using bytecode commands instead of native-code commands ? Could > you ask the two tools to display the commands they are calling, to > understand the difference ? My main goal was to get rid of ocamlbuild. So, case solved, I won't invest more time in that, sorry. -- Best regards, Francois Berenger.