From: Lee Revell <rlrevell@joe-job.com>
To: Con Kolivas <kernel@kolivas.org>
Cc: gcoady@gmail.com, linux-kernel@vger.kernel.org
Subject: Re: 2.6 vs 2.4, ssh terminal slowdown
Date: Wed, 08 Feb 2006 02:43:58 -0500 [thread overview]
Message-ID: <1139384639.9244.96.camel@mindpipe> (raw)
In-Reply-To: <200602081400.59931.kernel@kolivas.org>
On Wed, 2006-02-08 at 14:00 +1100, Con Kolivas wrote:
> This is the terminal's fault. xterm et al use an algorithm to
> determine how fast your machine is and decide whether to jump scroll
> or smooth scroll. This algorithm is basically broken with the 2.6
> scheduler and it decides to mostly smooth scroll.
>
Hmm, I've been having a similar problem for ages. If I just do "ls" in
my home directory 10 or 20 times, approximately 20% of the time it's
"fast":
real 0m0.177s
user 0m0.028s
sys 0m0.027s
And the rest of the times it's "slow":
real 0m1.240s
user 0m0.036s
sys 0m0.040s
I rarely get anything in between - it's either ~1.2s or ~0.2s.
"time ls | cat" is always fast - 0.18 - 0.35s.
real 0m0.188s
user 0m0.014s
sys 0m0.018s
It has been this way as long as I can remember and it never made
sense...
Lee
next prev parent reply other threads:[~2006-02-08 7:44 UTC|newest]
Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-08 2:11 2.6 vs 2.4, ssh terminal slowdown Grant Coady
2006-02-08 2:24 ` Benjamin LaHaise
2006-02-08 2:50 ` Grant Coady
2006-02-08 3:02 ` Benjamin LaHaise
2006-02-08 2:35 ` Con Kolivas
2006-02-08 2:55 ` Grant Coady
2006-02-08 3:00 ` Con Kolivas
2006-02-08 4:12 ` Barry K. Nathan
2006-02-08 4:41 ` Grant Coady
2006-02-08 4:51 ` Grant Coady
2006-02-08 5:17 ` Willy Tarreau
2006-02-08 5:39 ` Grant Coady
2006-02-08 7:43 ` Lee Revell [this message]
2006-02-09 17:06 ` Jan Engelhardt
2006-02-09 20:06 ` Lee Revell
2006-02-10 6:35 ` MIke Galbraith
2006-02-12 13:47 ` MIke Galbraith
2006-02-12 19:03 ` Lee Revell
2006-02-12 21:36 ` MIke Galbraith
2006-02-12 23:23 ` Lee Revell
2006-02-12 23:39 ` Lee Revell
2006-02-13 3:09 ` MIke Galbraith
2006-02-13 3:39 ` Lee Revell
2006-02-13 4:59 ` MIke Galbraith
2006-02-13 5:05 ` Con Kolivas
2006-02-13 5:32 ` MIke Galbraith
2006-02-13 5:37 ` Con Kolivas
2006-02-13 5:57 ` MIke Galbraith
2006-02-13 6:08 ` Con Kolivas
2006-02-13 6:35 ` MIke Galbraith
2006-02-13 6:38 ` Lee Revell
2006-02-13 7:08 ` MIke Galbraith
2006-02-13 8:43 ` Lee Revell
2006-02-13 10:06 ` MIke Galbraith
2006-02-13 12:35 ` MIke Galbraith
2006-02-15 4:22 ` Lee Revell
2006-02-15 5:22 ` MIke Galbraith
2006-02-15 6:11 ` Lee Revell
2006-02-15 7:17 ` MIke Galbraith
2006-02-13 7:15 ` Con Kolivas
2006-02-13 7:41 ` 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=1139384639.9244.96.camel@mindpipe \
--to=rlrevell@joe-job.com \
--cc=gcoady@gmail.com \
--cc=kernel@kolivas.org \
--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