From: Ingo Molnar <mingo@elte.hu>
To: Kirill Korotaev <dev@sw.ru>
Cc: linux-kernel@vger.kernel.org
Subject: Re: CPU scheduler tests
Date: Fri, 25 Mar 2005 09:32:24 +0100 [thread overview]
Message-ID: <20050325083224.GA23407@elte.hu> (raw)
In-Reply-To: <4243C243.10401@sw.ru>
* Kirill Korotaev <dev@sw.ru> wrote:
> Can someone (Ingo?) recommend me CPU scheduler tests which are usually
> used to test CPU scheduler perfomance, context switch performance,
> SMP/migration/balancing performance etc.?
it's not really the microbenchmarks that matter (although they obviously
are part of the picture), but actual application performance. There are
dozens of workloads that matter. Kernel compilation timings are an
obvious priority :-), but there are other things like SPECsdet, STREAM,
dbt3-pgsql, kernbench, AIM7, various Java benchmarks and more.
now that scheduler changes have calmed down somewhat, we are mainly
looking for regressions, and are checking schedstats output to see how
'healthy' a given workload behaves.
Ingo
next prev parent reply other threads:[~2005-03-25 8:32 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-25 7:48 CPU scheduler tests Kirill Korotaev
2005-03-25 8:32 ` Ingo Molnar [this message]
2005-03-25 14:32 ` Richard Hubbell
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=20050325083224.GA23407@elte.hu \
--to=mingo@elte.hu \
--cc=dev@sw.ru \
--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