mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Prakash Punnoor <prakash@punnoor.de>
To: Christian <christiand59@web.de>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Sluggish system responsiveness on I/O
Date: Sat, 18 Nov 2006 14:25:16 +0100	[thread overview]
Message-ID: <200611181425.17024.prakash@punnoor.de> (raw)
In-Reply-To: <200611181412.29144.christiand59@web.de>

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

Am Samstag 18 November 2006 14:12 schrieb Christian:
> So I tried to nice the make and see what happens:
>
> nice 5 make -j4: Seems to make no difference. Heavy stuttering in glxgears
> and et
> nice 10 make -j4: Somewhat better but still unusable with et
>
> everything above nice 15 is usable. nice 19 has full interactivity, that
> means you can't make out a difference between no load and kernel compile
> while playing enemy-territory.
>
> I suspect that it has something to do with the priority boost for I/O hogs.
> But if this is a "general" scheduler problem, then why aren't more people
> complaining about this?

I complained about this a year ago, but not much has changed. :-( It gets esp 
bad if you copy GB size files (the writes are the problemmakers, less the 
reads) - no matter which io scheduler I use, though using deadline seems to 
lessen the impact a little bit. And I don't find it acceptable to have to 
play around with nice to get a responsible desktop, esp when one is using a 
GUI.

Cheers,
-- 
(°=                 =°)
//\ Prakash Punnoor /\\
V_/                 \_V

[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]

  reply	other threads:[~2006-11-18 13:24 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-11-18 13:12 Christian
2006-11-18 13:25 ` Prakash Punnoor [this message]
2006-11-18 14:40   ` Christian
2006-11-19  7:51 ` Mike Galbraith
2006-11-19 17:44   ` Lee Revell
2006-11-19 18:34     ` Mike Galbraith
2006-11-22 10:57       ` [rfc patch] " Mike Galbraith

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=200611181425.17024.prakash@punnoor.de \
    --to=prakash@punnoor.de \
    --cc=christiand59@web.de \
    --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

all inboxes | Powered by JetHome®