public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Fengguang Wu <fengguang.wu@gmail.com>
To: Helge Hafting <helge.hafting@aitel.hist.no>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: New readahead - ups and downs
Date: Wed, 28 Jun 2006 00:06:24 +0800	[thread overview]
Message-ID: <351424373.01759@ustc.edu.cn> (raw)
Message-ID: <20060627160624.GB6014@mail.ustc.edu.cn> (raw)
In-Reply-To: <44A12D84.5010400@aitel.hist.no>

Hi Helge,

Thanks for testing it out.
I'll check it when I have time(I'll be out for a week...).

Wu

On Tue, Jun 27, 2006 at 03:07:16PM +0200, Helge Hafting wrote:
> Many have noticed positive sides of the new readahead system.
> I too see that, bootup is quicker and starting a big app like firefox is
> also noticeable faster.
> 
> I made my own little io-intensive test, that shows a case where
> performance drops.
> 
> I boot the machine, and starts "debsums", a debian utility that
> checksums every file managed by debian package management.
> As soon as the machine starts swapping, I also start
> start a process that applies an mm-patch to the kernel tree, and
> times this.
> 
> This patching took 1m28s with cold cache, without debsums running.
> With the 2.6.15 kernel (old readahead), and debsums running, this
> took 2m20s to complete, and 360kB in swap at the worst.
> 
> With the new readahead in 2.6.17-mm3 I get 6m22s for patching,
> and 22MB in swap at the most.  Runs with mm1 and mm2 were
> similiar, 5-6 minutes patching and 22MB swap.
> 
> My patching clearly takes more times this way.  I don't know
> if debsums improved though, it could be as simple as a fairness
> issue.  Memory pressure definitely went up.
> 
> 
> Helge Hafting
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at  http://www.tux.org/lkml/

  reply	other threads:[~2006-06-27 16:06 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-06-27 13:07 New readahead - ups and downs Helge Hafting
     [not found] ` <20060627160624.GB6014@mail.ustc.edu.cn>
2006-06-27 16:06   ` Fengguang Wu [this message]
     [not found] ` <20060702235516.GA6034@mail.ustc.edu.cn>
2006-07-02 23:55   ` Fengguang Wu
2006-07-03 13:50   ` New readahead - ups and downs new test Helge Hafting
     [not found]     ` <20060703153930.GC5874@mail.ustc.edu.cn>
2006-07-03 15:39       ` Fengguang Wu
2006-07-03 20:36       ` Helge Hafting
2006-07-03 21:42       ` New readahead - ups and downs new test. Vm oddities Helge Hafting
     [not found]         ` <20060704012621.GA7236@mail.ustc.edu.cn>
2006-07-04  1:26           ` Fengguang Wu

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=351424373.01759@ustc.edu.cn \
    --to=fengguang.wu@gmail.com \
    --cc=helge.hafting@aitel.hist.no \
    --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