From: Andrew Morton <akpm@digeo.com>
To: Benjamin LaHaise <bcrl@redhat.com>
Cc: Steven Cole <elenstev@mesatop.com>,
Linux Kernel <linux-kernel@vger.kernel.org>,
Alan Cox <alan@lxorguk.ukuu.org.uk>
Subject: Re: 2.5.44-[mm3, ac2] time to tar zxf kernel tarball compared forvarious fs.
Date: Wed, 23 Oct 2002 13:09:43 -0700 [thread overview]
Message-ID: <3DB70207.FBB38A0D@digeo.com> (raw)
In-Reply-To: 20021023160450.E3750@redhat.com
Benjamin LaHaise wrote:
>
> On Wed, Oct 23, 2002 at 12:57:24PM -0700, Andrew Morton wrote:
> > Steven Cole wrote:
> > >
> > > ext3
> > > tar zxf linux-2.5.44.tar.gz 2.5.44-mm3 2.5.44-ac2
> > > user 4.42 4.39
> > > system 4.09 4.05
> > > elapsed 00:53.17 00:34.05
> > > % CPU 16 24
> >
> > The smaller fifo_batch setting hurts when there are competing
> > reads and writes on the same disk.
>
> Is the ext2/3 allocation heuristic fix in yet? That might swing things
> around again too.
>
Only for ext2, only in -mm. I havben't submitted the Orlov allocator
because Ted is playing with it.
ext3's five-second commit interval and limited journal size really
bite in this test. We end up doing most of the writeback within
the measurement period rather than after it.
next prev parent reply other threads:[~2002-10-23 20:03 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-23 19:42 2.5.44-[mm3, ac2] time to tar zxf kernel tarball compared for various fs Steven Cole
2002-10-23 19:57 ` 2.5.44-[mm3, ac2] time to tar zxf kernel tarball compared forvarious fs Andrew Morton
2002-10-23 20:04 ` Benjamin LaHaise
2002-10-23 20:09 ` Andrew Morton [this message]
2002-10-24 8:34 ` Daniel Phillips
2002-10-23 20:05 ` Steven Cole
2002-10-23 20:32 ` Steven Cole
2002-10-23 20:44 ` 2.5.44-[mm3, ac2] time to tar zxf kernel tarball comparedforvarious fs Andrew Morton
2002-10-24 3:10 ` 2.5.44-[mm3, ac2] time to tar zxf kernel tarball compared forvarious fs Hans Reiser
2002-10-24 9:54 ` 2.5.44-[mm3, ac2] time to tar zxf kernel tarball compared forvarious Henning P. Schmiedehausen
2002-10-24 11:37 ` Padraig Brady
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=3DB70207.FBB38A0D@digeo.com \
--to=akpm@digeo.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=bcrl@redhat.com \
--cc=elenstev@mesatop.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;
as well as URLs for NNTP newsgroup(s).