caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: Ville-Pertti Keinonen <will@exomi.com>
To: Alex Baretta <alex@barettadeit.com>
Cc: Jon Harrop <jon@ffconsultancy.com>, Ocaml <caml-list@inria.fr>
Subject: Re: [Caml-list] 32- and 64-bit performance
Date: Wed, 30 Mar 2005 11:00:58 +0300	[thread overview]
Message-ID: <1112169658.27768.1.camel@dsws> (raw)
In-Reply-To: <424A593A.5050608@barettadeit.com>

On Wed, 2005-03-30 at 09:46 +0200, Alex Baretta wrote:

> Why do you suppose is there *any* benchmark faster in 32 bit mode than 
> in 64 bit mode on the Athlon64? Since the AMD64 architecture is 
> generally better than IA32--were it only for the additional registers--I 
> would expect all benchmarks to run as fast or faster when compiled to 
> the AMD64 instruction set.

64-bit data structures (due to bigger pointers, alignment, and in OCaml
bigger default integers) are bigger, so things that are constrained by
memory bandwidth are obviously going to be faster as 32-bit.

On other architectures where you can use 32-bit or 64-bit that are
otherwise identical, 32-bit is generally faster.



  reply	other threads:[~2005-03-30  9:00 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-03-30  2:40 Jon Harrop
2005-03-30  7:46 ` [Caml-list] " Alex Baretta
2005-03-30  8:00   ` Ville-Pertti Keinonen [this message]
2005-03-30  8:41     ` Alex Baretta
2005-03-30  9:01       ` Ville-Pertti Keinonen
2005-03-30 12:53         ` Jon Harrop
2005-03-30 14:34           ` Ville-Pertti Keinonen
2005-03-30  8:10   ` Robert Roessler
2005-03-30  8:11   ` Alexander S. Usov
2005-03-30 13:46 ` Eijiro Sumii
2005-03-31 13:42   ` Jon Harrop
2005-03-31 15:05 ` Stefan Monnier
2005-03-31 18:40   ` [Caml-list] " Jon Harrop
2005-03-31 22:41     ` Richard Jones
2005-04-02 20:23     ` Stefan Monnier
2005-04-02 20:50       ` [Caml-list] " David Brown
2005-04-03 10:01         ` Ville-Pertti Keinonen

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=1112169658.27768.1.camel@dsws \
    --to=will@exomi.com \
    --cc=alex@barettadeit.com \
    --cc=caml-list@inria.fr \
    --cc=jon@ffconsultancy.com \
    /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).