Mailing list for all users of the OCaml language and system.
 help / color / mirror / Atom feed
From: "Will M. Farr" <farr@MIT.EDU>
To: Christophe TROESTLER <Christophe.Troestler@umh.ac.be>
Cc: caml-list@inria.fr
Subject: Re: [Caml-list] [Benchmark] NBody
Date: Mon, 7 Feb 2005 14:55:03 -0500	[thread overview]
Message-ID: <05666de9ff3face903514bf411230a8e@mit.edu> (raw)
In-Reply-To: <20050207.203659.94743120.Christophe.Troestler@umh.ac.be>

When I ran it on my system using Shark (a Mac OS X profiling 
application that doesn't require hooks in the app itself to get the 
information), the breakdown of the significant values was

48.1% in advance
34% in __sqrt (system function)
+ random stuff

I'm not sure, in light of this, why the aggressive inlining makes any 
difference.

Will

On 7 Feb 2005, at 2:36 PM, Christophe TROESTLER wrote:

> On Mon, 7 Feb 2005, "Will M. Farr" <farr@MIT.EDU> wrote:
>>
>> You might try profiling (using gprof); maybe it will give you an
>> idea where your time is being spent.
>
> I did that but I could not see anything: the important spot reads:
>
> -----------------------------------------------
>                 8.05    0.00 1000000/1000000     camlNbody__entry [5]
> [6]     99.7    8.05    0.00 1000000         camlNbody__code_begin [6]
> -----------------------------------------------
>
> Did I miss something???
>
>> it looks like the java code is faster, but it clearly has a large
>> startup time.
>
> I thought that.  Still, I'd like to know whether there is a way to
> make Caml code that fast or if not why.
>
> Thanks for youe reply,
> ChriS


  reply	other threads:[~2005-02-07 19:55 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 [this message]
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
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=05666de9ff3face903514bf411230a8e@mit.edu \
    --to=farr@mit.edu \
    --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