caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: Jon Harrop <jon@ffconsultancy.com>
To: caml-list@yquem.inria.fr
Subject: x86 vs AMD64 OCaml compiler performance
Date: Wed, 6 Jul 2005 03:53:28 +0100	[thread overview]
Message-ID: <200507060353.29648.jon@ffconsultancy.com> (raw)


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.

Any ideas why?

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


             reply	other threads:[~2005-07-06  2:55 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-07-06  2:53 Jon Harrop [this message]
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
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=200507060353.29648.jon@ffconsultancy.com \
    --to=jon@ffconsultancy.com \
    --cc=caml-list@yquem.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).