From: Michael Gerdau <mgd@technosis.de>
To: Ingo Molnar <mingo@elte.hu>
Cc: linux-kernel@vger.kernel.org,
Linus Torvalds <torvalds@linux-foundation.org>,
Nick Piggin <npiggin@suse.de>,
Gene Heskett <gene.heskett@gmail.com>,
Juliusz Chroboczek <jch@pps.jussieu.fr>,
Mike Galbraith <efault@gmx.de>,
Peter Williams <pwil3058@bigpond.net.au>,
ck list <ck@vds.kolivas.org>,
Thomas Gleixner <tglx@linutronix.de>,
William Lee Irwin III <wli@holomorphy.com>,
Andrew Morton <akpm@linux-foundation.org>,
Bill Davidsen <davidsen@tmr.com>, Willy Tarreau <w@1wt.eu>,
Arjan van de Ven <arjan@infradead.org>
Subject: Re: [REPORT] cfs-v5 vs sd-0.46
Date: Tue, 24 Apr 2007 11:06:29 +0200 [thread overview]
Message-ID: <200704241106.41912.mgd@technosis.de> (raw)
In-Reply-To: <20070424085105.GA12329@elte.hu>
[-- Attachment #1: Type: text/plain, Size: 1132 bytes --]
> oh, you are writing the number-cruncher?
Yep.
> In general the 'best'
> performance metrics for scheduler validation are the ones where you have
> immediate feedback: i.e. some ops/sec (or ops per minute) value in some
> readily accessible place, or some "milliseconds-per-100,000 ops" type of
> metric - whichever lends itself better to the workload at hand.
I'll have to see whether that works out. I don't have an easily
available ops/sec but I guess I could create something similar.
> If you
> measure time then the best is to use long long and nanoseconds and the
> monotonic clocksource:
[snip]
Thanks, I will implement that, for Linux anyway.
> Plus an absolute metric of "the whole workload took X.Y seconds" is
> useful too.
That's the easiest to come by and is already available.
Best,
Michael
--
Technosis GmbH, Geschäftsführer: Michael Gerdau, Tobias Dittmar
Sitz Hamburg; HRB 89145 Amtsgericht Hamburg
Vote against SPAM - see http://www.politik-digital.de/spam/
Michael Gerdau email: mgd@technosis.de
GPG-keys available on request or at public keyserver
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2007-04-24 9:06 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-24 7:37 [REPORT] cfs-v5 vs sd-0.46 Michael Gerdau
2007-04-24 7:53 ` Ingo Molnar
2007-04-24 8:16 ` Michael Gerdau
2007-04-24 8:23 ` Ingo Molnar
2007-04-24 8:41 ` Michael Gerdau
2007-04-24 8:51 ` Ingo Molnar
2007-04-24 9:06 ` Michael Gerdau [this message]
2007-04-26 1:06 ` [ck] " Con Kolivas
2007-04-26 6:10 ` Michael Gerdau
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=200704241106.41912.mgd@technosis.de \
--to=mgd@technosis.de \
--cc=akpm@linux-foundation.org \
--cc=arjan@infradead.org \
--cc=ck@vds.kolivas.org \
--cc=davidsen@tmr.com \
--cc=efault@gmx.de \
--cc=gene.heskett@gmail.com \
--cc=jch@pps.jussieu.fr \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=npiggin@suse.de \
--cc=pwil3058@bigpond.net.au \
--cc=tglx@linutronix.de \
--cc=torvalds@linux-foundation.org \
--cc=w@1wt.eu \
--cc=wli@holomorphy.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.