From: "David Allsopp" <dra-news@metastack.com>
To: "'OCaml Mailing List'" <caml-list@inria.fr>
Subject: ocamlopt performance in 3.11
Date: Fri, 17 Oct 2008 11:59:22 +0200 [thread overview]
Message-ID: <57EBE30ABB324436B98173D41A9473CA@countertenor> (raw)
Pleased to say that I've got my 3 current projects compiled and running
under 3.11+beta1
Unfortunately for one of the projects, its "reference" run (a
computationally intensive, repeatable operation the speed of which interests
me) has gone from repeatedly taking ~38 seconds in 3.10.2 to ~46 seconds in
3.11.0+beta1. The other two projects don't have as easy a way for me to
calibrate speed (they spend most of their time blocked on I/O anyway!).
Has anything apart from the linker changed much in the 3.11 code generator
and has anyone else noticed a performance drop in any other programs?
David
(Machine setup: Windows XP SP3 + MinGW/gcc 3.4.4 running on an Intel Core
Duo T7200 @ 2GHz with 2GB RAM)
next reply other threads:[~2008-10-17 9:59 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-17 9:59 David Allsopp [this message]
2008-10-17 12:32 ` [Caml-list] " Andres Varon
2008-10-18 16:36 ` David Allsopp
2008-10-20 8:15 ` Alain
2008-10-20 12:11 ` David Allsopp
2008-10-31 23:58 ` Jon Harrop
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=57EBE30ABB324436B98173D41A9473CA@countertenor \
--to=dra-news@metastack.com \
--cc=caml-list@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;
as well as URLs for NNTP newsgroup(s).