caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: "Markus Mottl" <markus.mottl@gmail.com>
To: ocaml <caml-list@inria.fr>
Cc: "yaron jane" <yminsky@janestcapital.com>
Subject: Re: [Caml-list] Slow allocations with 64bit code?
Date: Mon, 23 Apr 2007 16:13:11 -0400	[thread overview]
Message-ID: <f8560b80704231313s3c7ffeb3n1da35ea5e2ddbc73@mail.gmail.com> (raw)
In-Reply-To: <f8560b80704220912v3ad2a4bfy9ed91f38a98072d3@mail.gmail.com>

On 4/22/07, Markus Mottl <markus.mottl@gmail.com> wrote:
> On 4/22/07, Xavier Leroy <Xavier.Leroy@inria.fr> wrote:
> > Be careful with timings: I've seen simple changes in code placement
> > (e.g. introducing or removing dead code) cause performance differences
> > in excess of 20%.  It's an unfortunate fact of today's processors that
> > their performance is very hard to predict.

After performing many extensive tests between 32bit/64bit platforms,
it seems that indeed code placement is a major cause of many if not
most timing differences I have seen, especially if the difference is
unusually big.

Other developers who want to make their code run fast independent of
platform should therefore be cautioned that a program compiled for
different architectures may be slower/faster for very random reasons
that have nothing to do with not having optimized well enough for the
special case.  This is especially true for low-level code, where such
effects do not cancel each other out easily.

Regards,
Markus

-- 
Markus Mottl        http://www.ocaml.info        markus.mottl@gmail.com


      reply	other threads:[~2007-04-23 20:13 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-04-20 20:31 Markus Mottl
2007-04-20 20:42 ` [Caml-list] " Jon Harrop
2007-04-21  2:57 ` skaller
2007-04-22 10:23 ` Xavier Leroy
2007-04-22 16:12   ` Markus Mottl
2007-04-23 20:13     ` Markus Mottl [this message]

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=f8560b80704231313s3c7ffeb3n1da35ea5e2ddbc73@mail.gmail.com \
    --to=markus.mottl@gmail.com \
    --cc=caml-list@inria.fr \
    --cc=yminsky@janestcapital.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).