From: Martin Jambon <martin_jambon@emailuser.net>
To: Christophe TROESTLER <Christophe.Troestler@umh.ac.be>
Cc: caml-list@inria.fr
Subject: Re: [Caml-list] [Benchmark] NBody
Date: Mon, 7 Feb 2005 12:22:55 -0800 (PST) [thread overview]
Message-ID: <Pine.LNX.4.44.0502071155160.2348-100000@localhost> (raw)
In-Reply-To: <20050207.204610.93889282.Christophe.Troestler@umh.ac.be>
On Mon, 7 Feb 2005, Christophe TROESTLER wrote:
> On Mon, 7 Feb 2005, Martin Jambon <martin_jambon@emailuser.net> wrote:
> >
> > On Mon, 7 Feb 2005, Christophe TROESTLER wrote:
> >
> > > ocamlopt -o nbody.com -inline 3 -unsafe -ccopt -O2 nbody.ml
> >
> > -inline 100 gives better results for me (around -25%)
>
> For me it is slower (about 13-18%). Are you also on an intel
> platform?
That was on my laptop with an Intel Celeron with Linux (I don't know much
more about the hardware). The results are stable.
I tested the same code on another machine with an Intel Pentium 4, and I
get "discrete" results. I repeat "time prog arg" in the shell
successively and get this:
time ./nbody-inline100 1_000_000
-> either 1.145-1.150 or 1.070-1.090 or sometimes 1.014-1.015
time ./nbody-inline3 1_000_000
-> either 0.990-0.995 or 1.245-1.255
This is an interesting effect... Probably it is well-known by people who
write compilers, personally I don't know anything about this topic. I can
provide more quantitative data on demand.
Martin
--
Martin Jambon, PhD
Researcher in Structural Bioinformatics since the 20th Century
The Burnham Institute http://www.burnham.org
San Diego, California
next prev parent reply other threads:[~2005-02-07 20:23 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-02-07 18:57 Christophe TROESTLER
2005-02-07 19:16 ` [Caml-list] " Will M. Farr
2005-02-07 19:36 ` Christophe TROESTLER
2005-02-07 19:55 ` Will M. Farr
2005-02-08 10:34 ` Olivier Andrieu
2005-02-08 10:52 ` Micha
2005-02-07 20:16 ` Markus Mottl
2005-02-07 19:37 ` Martin Jambon
2005-02-07 19:46 ` Christophe TROESTLER
2005-02-07 20:22 ` Martin Jambon [this message]
2005-02-07 20:04 ` sejourne_kevin
2005-02-07 20:32 ` Robert Roessler
2005-02-07 22:57 ` Oliver Bandel
2005-02-08 1:29 ` skaller
2005-02-08 1:48 ` Will M. Farr
2005-02-08 9:01 ` Ville-Pertti Keinonen
2005-02-08 9:37 ` skaller
2005-02-08 10:10 ` Ville-Pertti Keinonen
2005-02-08 16:36 ` skaller
2005-02-08 12:04 ` Marcin 'Qrczak' Kowalczyk
2005-02-08 17:06 ` skaller
2005-02-08 10:25 ` Xavier Leroy
2005-02-08 18:34 ` skaller
2005-02-08 10:43 ` Xavier Leroy
2005-02-08 11:26 ` Ville-Pertti Keinonen
2005-02-08 15:59 ` Florian Hars
2005-02-13 16:40 ` Christoph Bauer
2005-02-13 18:13 ` Christophe TROESTLER
2005-02-24 22:18 ` NBody (one more question) Christophe TROESTLER
2005-02-25 17:06 ` [Caml-list] " John Carr
2005-02-25 17:17 ` Christophe TROESTLER
2005-02-26 16:08 ` John Carr
2005-02-25 17:24 ` Ken Rose
2005-02-25 17:42 ` Oliver Bandel
2005-02-25 17:57 ` Xavier Leroy
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=Pine.LNX.4.44.0502071155160.2348-100000@localhost \
--to=martin_jambon@emailuser.net \
--cc=Christophe.Troestler@umh.ac.be \
--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