From: "David McClain" <dmcclain@azstarnet.com>
To: "Liste CAML" <caml-list@inria.fr>
Subject: Speedup from 2.01 to 2.02
Date: Fri, 5 Mar 1999 18:18:15 -0700 [thread overview]
Message-ID: <000b01be676f$375fd250$210148bf@dylan> (raw)
I have just recompiled my BlurFit routine under OcamlOpt 2.02. This version
is a completely new and far more sophisticated version than the one I
developed in December in only 3 days. However, its timing is still dominated
by large numeric array operations, and I would expect no increase in
performce for those inner tight loops.
The non-numeric overhead has been measured at 0.28 sec/iteration under
OCamlOpt 2.01 and 0.6 sec/iteration for the numeric operations.
Under OcamlOpt 2.02 the same program executes in 0.85 sec/iteration, for an
apparent speedup of roughly 10% in the non-numeric OCAML overhead code.
I think this is very good indeed. But I am posting this for the benefit of
the developers who may be interested in how their changes affect real-life
programs. I would be interested to hear from others regarding the speed
improvements.
David McClain
Sr. Scientist
Raytheon Missile Systems Co.
Tucson, AZ
http://www.azstarnet.com/~dmcclain/homepage.htm
reply other threads:[~1999-03-08 8:00 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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='000b01be676f$375fd250$210148bf@dylan' \
--to=dmcclain@azstarnet.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