From: Roger Larsson <roger.larsson@skelleftea.mail.telia.com>
To: Christoph Stueckjuergen <christoph.stueckjuergen@siemens.com>,
Robert Love <rml@tech9.net>
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.6.1 Scheduler Latency Measurements (Preemption diabled/enabled)
Date: Wed, 18 Feb 2004 22:00:04 +0100 [thread overview]
Message-ID: <200402182200.04754.roger.larsson@skelleftea.mail.telia.com> (raw)
Christoph Stueckjuergen wrote:
>Hi,
>
>I performed a series of measurements comparing scheduler latency of a 2.6.1
>kernel with preemption enabled and disabled on an AMD Elan (i486 compatible)
>with 133 Mhz clock frequency.
OK, then you have worse hardware than I had when I started to measure
latency :-)
> - - - interesting way of trigger and measure deleted - - -
> The results are:
> "loaded" system, 10.000 samples
> average scheduler latency (preemption enabled / disabled): 170 us / 232 us
> minimum scheduler latency (preemption enabled / disabled): 49 us / 43 us
> maximum scheduler latency (preemption enabled / disabled): 840 us / 1063 us
>
> "unloaded" system, 10.000 samples
> average scheduler latency (preemption enabled / disabled): 50 us / 44 us
> minimum scheduler latency (preemption enabled / disabled): 46 us / 41 us
> maximum scheduler latency (preemption enabled / disabled): 233 us / 215 us
>
Robert Love said:
> That said, I would of expected slightly better numbers.
I would say that the numbers are quite good :-)
For comparation check
http://www.gardena.net/benno/linux/audio/
There are some load tests there that you can use
to generate load: disk access, memory pressure, X11, ...
Note that more memory can result in worse latency, longer linked lists
to walk...
/RogerL
--
Roger Larsson
Skellefteå
Sweden
next reply other threads:[~2004-02-19 7:55 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-18 21:00 Roger Larsson [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-02-03 16:24 Christoph Stueckjuergen
2004-02-04 0:19 ` Nick Piggin
2004-02-04 0:37 ` Robert Love
2004-02-18 3:41 ` Bill Davidsen
2004-02-18 4:07 ` Nick Piggin
2004-02-18 7:42 ` Christoph Stueckjuergen
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=200402182200.04754.roger.larsson@skelleftea.mail.telia.com \
--to=roger.larsson@skelleftea.mail.telia.com \
--cc=christoph.stueckjuergen@siemens.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rml@tech9.net \
/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®