mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Felipe Alfaro Solana <felipe_alfaro@linuxmail.org>
To: Nick Piggin <piggin@cyberone.com.au>
Cc: linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: [RFC] renicing X
Date: Mon, 25 Aug 2003 19:12:08 +0200	[thread overview]
Message-ID: <1061831528.2967.7.camel@teapot.felipe-alfaro.com> (raw)
In-Reply-To: <3F4A3293.8070004@cyberone.com.au>

On Mon, 2003-08-25 at 18:00, Nick Piggin wrote:
> My scheduler patch really benefits a lot from renicing X. I
> think its because it nices more nicely. Any reasons why this
> might be a bad idea?

Well, not for me... Although renicing X with Con patches makes X feel
horrible, with your patches is not as horrible. However, I feel X much
smoother with X reniced at +0. Renicing X at -20, for example, may
reduce mouse cursor jumpiness under load, but makes X feel a little
jerky in general (window movement is not as smooth as with X niced at
+0). This is, however, based on subjective testing, not actual numbers.
But for interactivity, most of the time it's the subjective feeling of
the user about the system what matters, not numbers.

And now we're talking about sched-policy-7a: under heavy load, spawning
new processes still takes twice the time it takes when the system is
under no load. For example, spawning a new Konsole session (not a new
Konsole process, but a new session tab inside Konsole) takes approx. 1
second on my P3-700Mhz. However, with sched-policy-7a and under heavy
load (the mad while true; do a=2; done loop), it takes more than 2
seconds.

In general, sched-policy-7a feels extremely smooth and responsive in
general but, for me, Con patches offer the smoothest X experience I have
ever felt until date. Anyways, I will keep testing your patches and I
greatly encourage you to keep improving them. It's always good to have
diversity :-)


  reply	other threads:[~2003-08-25 17:12 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-08-25 16:00 Nick Piggin
2003-08-25 17:12 ` Felipe Alfaro Solana [this message]
2003-08-25 17:37   ` Nick Piggin

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=1061831528.2967.7.camel@teapot.felipe-alfaro.com \
    --to=felipe_alfaro@linuxmail.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=piggin@cyberone.com.au \
    /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®