caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: Jon Harrop <jon@ffconsultancy.com>
To: Caml-list <caml-list@inria.fr>
Subject: Re: [Caml-list] x86 vs AMD64 OCaml compiler performance
Date: Wed, 6 Jul 2005 18:31:51 +0100	[thread overview]
Message-ID: <200507061831.51964.jon@ffconsultancy.com> (raw)
In-Reply-To: <42CC11E8.8040505@rftp.com>

On Wednesday 06 July 2005 18:16, you wrote:
> Jon Harrop wrote:
> > I just timed recompilation of my latest project to both byte code and
> > native code on both 900MHz Athlon t-bird and 800MHz Athlon64. To my
> > suprise, compilation to native code takes roughly the same amount of time
> > on both computers but compilation to byte code is slightly faster (1m18
> > vs 1m40) on x86 but vastly faster (21s vs 1m50) on AMD64.
>
> Ummm... do you mean "1800MHz" or "1.8GHz" for the Athlon64? :)

No, I got that bit right - 800MHz (downclocked for the muggy summer). Running 
at 1.8GHz it compiles in 9s but overheats and switches off after a few 
minutes, especially when the GPU is working like a Trojan.

With compilers compiled to native code I now get:

              ocamlc ocamlopt
800MHz AMD64     18s      24s
1.8GHz AMD64      9s      12s
900MHz Athlon    27s      34s

I'd have expected the compilers to be doing mostly tree manipulation so I was 
expecting the AMD64 to perform poorly, as the tree-intensive Set.union was 
the only benchmark where my AMD64 was slower in 64-bit mode than in 32-bit 
mode. In fact, the AMD64 is no slouch.

The vast majority of the time is spent compiling only a few of the source 
files. Four of them are autogenerated and just contain 300kB of data each, so 
it's no surprise those are slow. The other is my implementation of a scene 
graph. Although it is very elegant and actually works very well, many of the 
types are half a page long, so my guess is that the time is spent in the type 
system there.

-- 
Dr Jon D Harrop, Flying Frog Consultancy Ltd.
Technical Presentation Software
http://www.ffconsultancy.com/products/presenta


  reply	other threads:[~2005-07-06 17:33 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-07-06  2:53 Jon Harrop
2005-07-06  6:44 ` [Caml-list] " Florian Hars
2005-07-06 16:20   ` Jon Harrop
2005-07-06 17:16 ` Robert Roessler
2005-07-06 17:31   ` Jon Harrop [this message]
2005-07-06 19:18     ` Christopher Campbell

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=200507061831.51964.jon@ffconsultancy.com \
    --to=jon@ffconsultancy.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).