public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: R.E.Wolff@BitWizard.nl (Rogier Wolff)
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: Gerhard Mack <gmack@innerfire.net>,
	Rik van Riel <riel@conectiva.com.br>,
	John Fremlin <vii@penguinpowered.com>,
	scole@lanl.gov, linux-kernel@vger.kernel.org
Subject: Re: UP 2.2.18 makes kernels 3% faster than UP 2.4.0-test12
Date: Wed, 13 Dec 2000 10:44:38 +0100 (MET)	[thread overview]
Message-ID: <200012130944.KAA30595@cave.bitwizard.nl> (raw)
In-Reply-To: <E145b60-00007M-00@the-village.bc.nu> from Alan Cox at "Dec 11, 2000 10:06:54 pm"

Alan Cox wrote:
> > How much of that is due to the fact that the 2.4.0 scheduler interrupts
> > processes more often than 2.2.x?  Is the better interactivity worth the
> > slight drop in performance?
> 
> What better interactivity ;)

Indeed!

On my dual Celeron workstation, 2.4 looks to me as if it is scheduling
"more". Thus when I move a window, the window takes on all intervening
positions. Under 2.2, the window sometimes jerks 10 pixels or so, but
it acutally follows the mouse. Under 2.4, you can get hte window to
lag the mouse by a significant amount.

Thus to me, 2.4 FEELS much less interactive. When I move windows they
don't follow the mouse in real-time. 

				Roger.

-- 
** R.E.Wolff@BitWizard.nl ** http://www.BitWizard.nl/ ** +31-15-2137555 **
*-- BitWizard writes Linux device drivers for any device you may have! --*
* There are old pilots, and there are bold pilots. 
* There are also old, bald pilots. 
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/

  reply	other threads:[~2000-12-13 10:15 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-12-10 20:36 UP 2.2.18 makes kernels 3% faster than UP 2.4.0-test12 Steven Cole
2000-12-11 18:16 ` John Fremlin
2000-12-11 18:38   ` Rik van Riel
2000-12-11 18:46     ` Alan Cox
2000-12-11 19:50       ` Zdenek Kabelac
2000-12-11 20:15       ` Arjan van de Ven
2000-12-11 20:23       ` Rik van Riel
2000-12-11 22:03       ` Gerhard Mack
2000-12-11 22:06         ` Alan Cox
2000-12-13  9:44           ` Rogier Wolff [this message]
2000-12-14 13:08             ` Russell King
2000-12-16  0:40               ` george anzinger
2000-12-12 14:49         ` Steven Cole
2000-12-12 18:18       ` Steven Cole
2000-12-12 18:40         ` Linus Torvalds
2000-12-12 20:19           ` Steven Cole
2000-12-12 20:38             ` Linus Torvalds
2000-12-12 22:09               ` Steven Cole
2000-12-11 22:12     ` Gabor Lenart
  -- strict thread matches above, loose matches on Subject: below --
2000-12-10 15:31 Steven Cole
2000-12-10 19:52 ` Aaron Tiensivu
2000-12-11 23:02   ` Steven Cole
2000-12-12  4:40     ` Mike Galbraith
2000-12-12  5:17       ` Steven Cole
2000-12-12  5:20         ` Mike Galbraith
2000-12-12 11:01         ` Helge Hafting
2000-12-12 10:27     ` Rik van Riel
2000-12-12 14:15       ` 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=200012130944.KAA30595@cave.bitwizard.nl \
    --to=r.e.wolff@bitwizard.nl \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=gmack@innerfire.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=riel@conectiva.com.br \
    --cc=scole@lanl.gov \
    --cc=vii@penguinpowered.com \
    /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