public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Nick Piggin <nickpiggin@yahoo.com.au>
To: linux-kernel <linux-kernel@vger.kernel.org>
Subject: scheduler latency
Date: Thu, 29 Apr 2004 19:27:33 +1000	[thread overview]
Message-ID: <4090CA85.6050009@yahoo.com.au> (raw)

Hi,
I've done some scheduler latency tests and come up with some
pretty plots, so I thought I'd post them. It is nicksched vs
mainline.

Note: this is not realtime scheduling latency, but latency as
measured by my random program. It also does not indicate
interactivity, because the latencies measured were all under
15ms which is probably below perception. Even if not, it
doesn't measure latency as you might see it.

Finally, some of the tests involved me moving the mouse around,
so factor in by subliminal (or not) bias toward my scheduler.

http://www.kerneltrap.org/~npiggin/schedlat3/index.html

             reply	other threads:[~2004-04-29  9:27 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-04-29  9:27 Nick Piggin [this message]
2004-04-29 18:05 ` scheduler latency Davide Libenzi

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=4090CA85.6050009@yahoo.com.au \
    --to=nickpiggin@yahoo.com.au \
    --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