public inbox for linux-ia64@vger.kernel.org
 help / color / mirror / Atom feed
From: David Mosberger <davidm@napali.hpl.hp.com>
To: linux-ia64@vger.kernel.org
Subject: Re: Consistency problem on IPF
Date: Mon, 12 Jul 2004 20:37:52 +0000	[thread overview]
Message-ID: <16626.63136.533212.192276@napali.hpl.hp.com> (raw)
In-Reply-To: <40F2562C.10208@inria.fr>

>>>>> On Mon, 12 Jul 2004 14:01:15 +0200, Marc Gonzalez-Sigler <marc.gonzalez-sigler@inria.fr> said:

  Marc> (For the record, I tried gcc-3.3.4 and orcc-2.1)

For floating-point stuff, you'll definitely want to try the Intel compiler.
It's a free download for the unsupported/non-commercial version.

As others have pointed out, for matrix multiply, you'll definitely
want to use a hand-tuned version as is available in several math
libraries (yeah, I realize you are not really after matrix multiply).

  Marc> Perhaps I was not clear enough. I used matrix-matrix multiply
  Marc> only as an example. My real problem is the non-deterministic
  Marc> behavior.

Page-coloring can make things more deterministic, at the expense of making
_everything_ go slower.  If you search the net, you should be able to
find a page-coloring module.  We have experimented with it in the past
and it did its job, but it's overall impact was to slow things down, so
it's not a great solution.

The other thing you could do on Linux is use huge pages.  That will
mitigate/eliminate the effect of page coloring (and also reduce TLB
pressure).

  Marc> Say I tile the main loop nest. I want to compare the execution
  Marc> time of the original, untiled program and the execution time
  Marc> of the modified, tiled program.

  Marc> If the original version completes in 1 second 80% of the time,
  Marc> and the modified version completes in 0.5 seconds 80% of the
  Marc> time, but 2 seconds 20% of the time, then, if I am unlucky, I
  Marc> might eliminate an excellent candidate. This is why I need the
  Marc> execution times of a given program to be consistent.

I think you have to allow for the fact that modern CPUs (and OSes) do
not really offer deterministic performance.  And don't expect things
to get better.  Dynamic power throttling, multi-threading, etc., will
make performance analysis very "interesting".

	--david

  parent reply	other threads:[~2004-07-12 20:37 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-07-12  9:13 Consistency problem on IPF Marc Gonzalez-Sigler
2004-07-12 10:06 ` Erich Focht
2004-07-12 11:12 ` Duraid Madina
2004-07-12 11:24 ` Erich Focht
2004-07-12 11:39 ` Marc Gonzalez-Sigler
2004-07-12 12:01 ` Marc Gonzalez-Sigler
2004-07-12 20:37 ` David Mosberger [this message]
2004-07-12 21:49 ` Duraid Madina
2004-07-12 22:05 ` David Mosberger
2004-07-12 22:08 ` Rich Altmaier

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=16626.63136.533212.192276@napali.hpl.hp.com \
    --to=davidm@napali.hpl.hp.com \
    --cc=linux-ia64@vger.kernel.org \
    /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