From: Mark Shinwell <mshinwell@janestreet.com>
To: Nils Becker <nils.becker@bioquant.uni-heidelberg.de>
Cc: Gabriel Scherer <gabriel.scherer@gmail.com>,
caml users <caml-list@inria.fr>
Subject: Re: [Caml-list] flambda optimization settings
Date: Fri, 13 May 2016 09:27:34 +0100 [thread overview]
Message-ID: <CAM3Ki75obgpZW=4V7cdv-+iamzqYbjTg6KgyKwzSiiq_tkJfag@mail.gmail.com> (raw)
In-Reply-To: <5734DFBF.8070202@bioquant.uni-heidelberg.de>
Thanks for these numbers, which I think are about in line with expectations.
At present the optimisation flags such as -O3 only need to be
specified when compilation (rather than linking) is occurring. So if
your link command only lists previously-compiled files, there is no
need to specify such options.
Mark
On 12 May 2016 at 20:55, Nils Becker
<nils.becker@bioquant.uni-heidelberg.de> wrote:
>
>> Thus, it would be interesting and important to also compare with the
>> code produced by a 4.03 switch compiled without flambda.
>
> coming right up
>
> (different parameters, different machine, best of 5 -- it varies quite a
> lot)
>
> time (ocamlbuild -clean; ocamlbuild facs_run.native)
> 4.03.0 1.36s
> 4.03.0+flambda
> Oclassic 1.68s
> O2 2.1s
> O3 2.80s
>
>
> the actual run: time ./facs_run.native
>
> 4.03.0 23.3s
> 4.03.0+flambda
> Oclassic 24.2s
> O2 22.7s
> O3 20.1s
>
>
> so it seems compilation on flambda classic is still a bit slower than
> non-flambda; as is the run time. the gains of O3 over non-flambda are
> still significant, as is the difference O2 vs O3.
>
> n
>
> --
> Caml-list mailing list. Subscription management and archives:
> https://sympa.inria.fr/sympa/arc/caml-list
> Beginner's list: http://groups.yahoo.com/group/ocaml_beginners
> Bug reports: http://caml.inria.fr/bin/caml-bugs
next prev parent reply other threads:[~2016-05-13 8:27 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-12 16:13 Nils Becker
2016-05-12 18:25 ` Gabriel Scherer
2016-05-12 19:55 ` Nils Becker
2016-05-13 8:27 ` Mark Shinwell [this message]
2016-05-13 8:34 ` Nils Becker
2016-05-13 8:51 ` Mark Shinwell
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='CAM3Ki75obgpZW=4V7cdv-+iamzqYbjTg6KgyKwzSiiq_tkJfag@mail.gmail.com' \
--to=mshinwell@janestreet.com \
--cc=caml-list@inria.fr \
--cc=gabriel.scherer@gmail.com \
--cc=nils.becker@bioquant.uni-heidelberg.de \
/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