From: Jens Axboe <axboe@suse.de>
To: James <iphitus@gmail.com>
Cc: linux-kernel@vger.kernel.org, ck@vds.kolivas.org
Subject: Re: [PATCH] fcache: a remapping boot cache
Date: Sat, 24 Jun 2006 13:10:00 +0200 [thread overview]
Message-ID: <20060624110959.GQ4083@suse.de> (raw)
In-Reply-To: <1e1a7e1b0606232044x11136be5p332716b757ecd537@mail.gmail.com>
On Sat, Jun 24 2006, James wrote:
> Set this up on my laptop yesterday with some awesome results. I'm
> using 2.6.17-ck1 which has v2.1.
>
> Heres some bootcharts, before, after, and a prime run.
>
> http://archlinux.org/~james/normal.png
> http://archlinux.org/~james/fs-fcache.png
> http://archlinux.org/~james/fs-fcache-prime.png
>
> Repeated boots show about the same 6 second improvement, 32 down to 26
> seconds. Looking at the slowdowns in the fs-fcache run, most are due
> to cpu load, waiting on network or, modprobe, and not disk access. X
> now starts nearly instantaneously.
>
> As an experiment, I primed my cache right through to logging into my
> desktop environment. It was so effective, that now when I login, the
> GNOME splash screen only flickers onto the screen briefly, and the
> panels appear almost instantly. This is a big improvment over without
> fcache, where you'd see each component of GNOME being loaded on the
> splash screen, nautilus, metacity, and the panels would take quite a
> bit of time to render and load all their applets.
>
> Impressive work, I hope to see it broadened to other filesystems,
> improved and merged to vanilla soon because it has clear improvements.
Thanks for giving it a spin! I have plans to implement some improvements
on monday that will speed it up even more, I hope I can talk you into
retesting it then. Basically it make sure we always get full speed out
of the drive by extending the 4kb reads with a sliding window cache.
That will help both drive efficiency, and also speed up the cases where
sub sequent boots differ just a little bit from the primed boot (often
the case with parallel init scripts). It should win you a few seconds
more in total, would be my guess.
I hope to be able to extend it to xfs and reiser in the very near future
as well, should not be hard to do.
--
Jens Axboe
next prev parent reply other threads:[~2006-06-24 11:08 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-15 9:18 [PATCH] fcache: a remapping boot cache Jens Axboe
2006-05-15 10:10 ` Jens Axboe
2006-05-16 7:46 ` Jens Axboe
2006-05-30 21:38 ` Paolo Ciarrocchi
2006-05-31 6:12 ` Jens Axboe
2006-06-24 3:44 ` James
2006-06-24 11:10 ` Jens Axboe [this message]
2006-06-24 12:03 ` [ck] " André Goddard Rosa
2006-06-26 6:43 ` Jens Axboe
[not found] ` <fe15b94a0606260015i440c995vda3327cc3c4c8210@mail.gmail.com>
2006-06-26 7:21 ` Jens Axboe
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=20060624110959.GQ4083@suse.de \
--to=axboe@suse.de \
--cc=ck@vds.kolivas.org \
--cc=iphitus@gmail.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