From: Andi Kleen <andi@firstfloor.org>
To: Christoph Lameter <clameter@sgi.com>
Cc: Andi Kleen <andi@firstfloor.org>, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 2/7] Simple Performance Counters: x86_64 support
Date: Wed, 1 Aug 2007 20:26:11 +0200 [thread overview]
Message-ID: <20070801182611.GB20713@one.firstfloor.org> (raw)
In-Reply-To: <Pine.LNX.4.64.0708011052080.20795@schroedinger.engr.sgi.com>
> But then the numbers are not comparable across systems.
That would only matter if you're interested in absolute system
performance of different systems.
But comparable performance testing in general only makes sense when you
only change one variable: either you change the hardware or
you change the software. If you change both at the same time
you'll never know where the difference comes from.
I assume this facility is aimed at software performance testing:
this means it doesn't make much sense to compare numbers
between different systems; just relative numbers on the same
system with different software.
If you want absolute comparable system performance benchmarks I don't think
micro-instrumenting the kernel is a good approach.
But for relative performance cycles are fine. Anyways if you really
wanted to do ns it's possible too, but far more complicated to do correctly.
-Andi
next prev parent reply other threads:[~2007-08-01 18:26 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-31 23:25 Christoph Lameter
2007-08-01 10:53 ` Andi Kleen
2007-08-01 17:52 ` Christoph Lameter
2007-08-01 18:26 ` Andi Kleen [this message]
2007-08-01 18:29 ` Christoph Lameter
2007-08-01 18:40 ` Andi Kleen
2007-08-01 18:45 ` Christoph Lameter
2007-08-01 18:57 ` Andi Kleen
2007-08-01 18:58 ` Christoph Lameter
2007-08-01 19:15 ` Andi Kleen
2007-08-17 16:10 ` Mathieu Desnoyers
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=20070801182611.GB20713@one.firstfloor.org \
--to=andi@firstfloor.org \
--cc=clameter@sgi.com \
--cc=linux-kernel@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
all inboxes | Powered by JetHome®