mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: David Mansfield <lkml@dm.cobite.com>
To: Andrew Morton <akpm@digeo.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: very poor performance in 2.5.66[-mm1]
Date: Fri, 28 Mar 2003 16:54:26 -0500 (EST)	[thread overview]
Message-ID: <Pine.LNX.4.44.0303281641320.11928-100000@admin> (raw)
In-Reply-To: <20030328124451.2d09bd33.akpm@digeo.com>

On Fri, 28 Mar 2003, Andrew Morton wrote:
> > After all of the rave reviews about the interactivity fixes (both regular 
> > and I/O scheduler related), I decided to give the 2.5.latest a try on my 
> > desktop machine (system described below)
> > 
> > I started X, everything seemed fine, maybe a bit faster.  I opened a 
> > 'gnome-terminal' and typed 'ls -ltr'.  Wow, it was 20x slower.
> > 
> > Here are the timings for 'ls -ltr':
> > 
> > 2.5.66-mm1:      'ls -ltr'         31 seconds
> > 2.5.66-mm1:      'ls -ltr | cat'   2 seconds
> > 2.4.18-rhlatest: 'ls -ltr'         1.14 seconds
> 
> How many files were there?

1337 files.

> My /usr/bin contains 3168 files.  An `ls -ltr' in gnome-terminal takes 9.6
> seconds.  In rxvt it takes 0.5 seconds.  That's an 850MHz P3.
> 
> So gnome-terminal appears to be a pretty slow application.  My guess would be
> that something in the 2.5 kernel has exposed a marginality or an outright
> bug in it.

Yes. gnome-terminal is godawful slow on RHAT 8.0 (it does Xrender
alpha-channel crap for every character to get the anti-aliasing).  But I
think the problem has to do with the pipe/pty wakeups.  After 'ls' writes
a line to the pty, it seems as though the gnome-terminal is being woken up
(even though 'ls' has more to write), it's generating the Xrender 
X-command and sending it to X.  X is waking up and rendering it (which 
forces a complete update of the screen).

Under 2.4.18-whatever, it would seem as though 'ls' is generating a large
number of lines of output before the gnome-terminal is waking up, causing
a dramatically fewer number of redraws.

> It would be interesting to edit include/asm-i386/param.h and set HZ to 100.
> 

I'll try to check this out over the weekend.

David

-- 
/==============================\
| David Mansfield              |
| lkml@dm.cobite.com           |
\==============================/


  reply	other threads:[~2003-03-28 21:43 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-03-28 18:01 David Mansfield
2003-03-28 20:44 ` Andrew Morton
2003-03-28 21:54   ` David Mansfield [this message]
2003-03-28 22:01     ` jjs
2003-03-29  8:13     ` Ingo Molnar
2003-03-31  8:45 ` P

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=Pine.LNX.4.44.0303281641320.11928-100000@admin \
    --to=lkml@dm.cobite.com \
    --cc=akpm@digeo.com \
    --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®