From: Soeren Sonnenburg <kernel@nn7.de>
To: Linux Kernel <linux-kernel@vger.kernel.org>
Subject: xterm scrolling speed - scheduling weirdness in 2.6 ?!
Date: Sat, 03 Jan 2004 19:52:36 +0100 [thread overview]
Message-ID: <1073075108.9851.16.camel@localhost> (raw)
[-- Attachment #1: Type: text/plain, Size: 905 bytes --]
Hi...
I notice a severe speed regression with 2.6 and working in e.g. xterm on
X11 (no framebuffer device in use). It is all about scrolling speed. I
used to type e.g. just dmesg in a fullscreen xterm (or MGT) in 2.4 and
the whole output was there lightning fast, i.e.
in 2.4:
=======
time dmesg
real 0m0.096s
user 0m0.007s
sys 0m0.005s
in 2.6 (first run)
======
time dmesg
[...]
real 0m3.054s
user 0m0.008s
sys 0m0.008s
in 2.6 (second run)
===================
dmesg >d
time cat d
real 0m0.096s
user 0m0.002s
sys 0m0.005s
in 2.6 (third run)
==================
time dmesg
real 0m0.095s
user 0m0.007s
sys 0m0.004s
So it is like 30 times slower on 2.6. when running for the first time...
this also happens if I do e.g. find ./ and watch the output pass by...
This is without preemption on powerpc...
Anyone else with that problem - ideas of the cause ?
Soeren.
[-- Attachment #2: config.gz --]
[-- Type: application/x-gzip, Size: 7048 bytes --]
next reply other threads:[~2004-01-03 18:54 UTC|newest]
Thread overview: 56+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-03 18:52 Soeren Sonnenburg [this message]
2004-01-03 19:19 ` xterm scrolling speed - scheduling weirdness in 2.6 ?! Willy Tarreau
2004-01-04 20:47 ` Peter Chubb
2004-01-04 20:54 ` Willy TARREAU
2004-01-05 3:46 ` Peter Chubb
[not found] <Pine.LNX.4.44.0401031402210.24942-100000@coffee.psychology.mcmaster.ca>
2004-01-03 19:07 ` Soeren Sonnenburg
[not found] <Pine.LNX.4.44.0401031439060.24942-100000@coffee.psychology.mcmaster.ca>
2004-01-03 20:19 ` Soeren Sonnenburg
2004-01-03 21:00 ` Con Kolivas
2004-01-03 21:10 ` Soeren Sonnenburg
2004-01-03 21:15 ` Con Kolivas
2004-01-03 23:35 ` Willy Tarreau
2004-01-04 0:11 ` Soeren Sonnenburg
2004-01-04 1:42 ` Con Kolivas
2004-01-04 3:32 ` Tim Connors
2004-01-04 5:58 ` Con Kolivas
2004-01-06 1:09 ` Peter Osterlund
2004-01-06 1:37 ` Nick Piggin
2004-01-06 2:28 ` Peter Osterlund
2004-01-06 2:50 ` Nick Piggin
2004-01-06 6:27 ` Nick Piggin
2004-01-05 22:25 ` Bryan Whitehead
2004-01-04 8:09 ` Soeren Sonnenburg
2004-01-04 8:49 ` Con Kolivas
2004-01-04 11:13 ` Martin Schlemmer
2004-01-04 11:24 ` Soeren Sonnenburg
2004-01-04 12:45 ` Con Kolivas
2004-01-04 14:42 ` Martin Schlemmer
2004-01-04 18:40 ` mikeg
2004-01-04 22:58 ` szonyi calin
2004-01-04 23:33 ` Willy Tarreau
2004-01-04 23:44 ` Valdis.Kletnieks
2004-01-04 23:47 ` Mike Fedyk
2004-01-05 8:39 ` Soeren Sonnenburg
2004-01-05 20:38 ` Martin Schlemmer
2004-01-05 9:18 ` Soeren Sonnenburg
2004-01-05 17:20 ` Martin Schlemmer
2004-01-05 17:21 ` Willy Tarreau
2004-01-05 9:50 ` Kenneth Johansson
2004-01-05 10:17 ` Soeren Sonnenburg
2004-01-05 8:26 ` Soeren Sonnenburg
2004-01-04 8:54 ` Lincoln Dale
2004-01-04 9:17 ` Nick Piggin
2004-01-04 10:24 ` Soeren Sonnenburg
2004-01-04 11:12 ` Mike Fedyk
2004-01-04 11:17 ` Soeren Sonnenburg
2004-01-04 11:20 ` Mike Fedyk
2004-01-04 11:19 ` Willy Tarreau
2004-01-05 0:48 ` Nick Piggin
2004-01-04 12:07 ` Willy Tarreau
2004-01-05 0:51 ` Nick Piggin
2004-01-05 18:37 ` Willy Tarreau
2004-01-06 0:33 ` Nick Piggin
2004-01-04 10:11 ` Soeren Sonnenburg
2004-01-05 10:31 ` venom
2004-01-03 21:18 ` Willy Tarreau
-- strict thread matches above, loose matches on Subject: below --
2004-01-03 21:39 Bob Gill
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=1073075108.9851.16.camel@localhost \
--to=kernel@nn7.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 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.