All of lore.kernel.org
 help / color / mirror / Atom feed
From: Dan Chen <crimsun@email.unc.edu>
To: Shawn Starr <spstarr@sh0n.net>
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.4.18-pre8 + 2.4.17-pre8-ac3 + rmap12c + XFS Results
Date: Wed, 6 Feb 2002 04:13:38 -0500	[thread overview]
Message-ID: <20020206091338.GA670@opeth.ath.cx> (raw)
In-Reply-To: <Pine.LNX.4.40.0202060213380.395-100000@coredump.sh0n.net>
In-Reply-To: <Pine.LNX.4.40.0202060213380.395-100000@coredump.sh0n.net>

[-- Attachment #1: Type: text/plain, Size: 849 bytes --]

On Wed, Feb 06, 2002 at 02:17:28AM -0500, Shawn Starr wrote:
> I'm happy to say that rmap12c has huge preformance improvements over
> rmap11c with my Pentium 200Mhz w/64MB ram.
> 
> Some of the differences:
> 
> rmap11c: slow redrawing of mozilla, mouse hangs, system sluggishness.
> 
> rmap12c: no slow redrawing UNLESS heavy I/O & swapping is occuring. System
                                    ^^^^^^^^^^^^^^^^^^^^
Would you try the ChangeSet 1.188, specifically the one for
fs/buffer.c@1.52?
http://linuxvm.bkbits.net:8088/vm-2.4/diffs/fs/buffer.c@1.52?nav=index.html|ChangeSet@-2d|cset@1.188

I agree that rmap12c + the above fix has noticeable improvements over
the 11 series. I'll be pushing some numbers out later today.

-- 
Dan Chen                 crimsun@email.unc.edu
GPG key:   www.unc.edu/~crimsun/pubkey.gpg.asc

[-- Attachment #2: Type: application/pgp-signature, Size: 232 bytes --]

  parent reply	other threads:[~2002-02-06  9:14 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-02-06  7:17 2.4.18-pre8 + 2.4.17-pre8-ac3 + rmap12c + XFS Results Shawn Starr
2002-02-06  8:23 ` Shawn
2002-02-06  8:50   ` 2.4.18-pre8 + 2.4.18-pre7-ac3 " Shawn Starr
2002-02-06  9:13 ` Dan Chen [this message]
2002-02-06 13:07   ` 2.4.18-pre8 + 2.4.17-pre8-ac3 " William Lee Irwin III
2002-02-06 15:26   ` Shawn Starr

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=20020206091338.GA670@opeth.ath.cx \
    --to=crimsun@email.unc.edu \
    --cc=linux-kernel@vger.kernel.org \
    --cc=spstarr@sh0n.net \
    /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.