All of lore.kernel.org
 help / color / mirror / Atom feed
From: Bill Davidsen <davidsen@tmr.com>
To: Linux Kernel M/L <linux-kernel@vger.kernel.org>
Subject: [RFC] another scheduler beater
Date: Mon, 23 Apr 2007 17:55:26 -0400	[thread overview]
Message-ID: <462D2B4E.7050009@tmr.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 582 bytes --]

The small attached script does a nice job of showing animation glitches 
in the glxgears animation. I have run one set of tests, and will have 
several more tomorrow. I'm off to a poker game, and would like to let 
people draw their own conclusions.

Based on just this script as load I would say renice on X isn't a good 
thing. Based on one small test, I would say that renice of X in 
conjunction with heavy disk i/o and a single fast scrolling xterm (think 
kernel compile) seems to slow the raid6 thread measurably. Results late 
tomorrow, it will be an early and long day :-(

[-- Attachment #2: glitch1.sh --]
[-- Type: application/x-sh, Size: 377 bytes --]

             reply	other threads:[~2007-04-23 22:20 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-04-23 21:55 Bill Davidsen [this message]
2007-04-24  4:36 ` [RFC] another scheduler beater Mike Galbraith
2007-04-24  8:17 ` Ingo Molnar
2007-04-24 12:06   ` Ed Tomlinson

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=462D2B4E.7050009@tmr.com \
    --to=davidsen@tmr.com \
    --cc=davidsen@posidon.tmr.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 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.