public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@linux-foundation.org>
To: Arjan van de Ven <arjan@infradead.org>
Cc: Ingo Molnar <mingo@elte.hu>,
	spamtrap@knobisoft.de, linux-kernel@vger.kernel.org,
	a.p.zijlstra@chello.nl, wfg@mail.ustc.edu.cn,
	torvalds@linux-foundation.org, riel@redhat.com
Subject: Re: 2.6.24-rc1: First impressions
Date: Fri, 26 Oct 2007 22:59:51 -0700	[thread overview]
Message-ID: <20071026225951.db374baf.akpm@linux-foundation.org> (raw)
In-Reply-To: <20071026224657.11dcf950@laptopd505.fenrus.org>

On Fri, 26 Oct 2007 22:46:57 -0700 Arjan van de Ven <arjan@infradead.org> wrote:

> > > > dd1 - copy 16 GB from /dev/zero to local FS
> > > > dd1-dir - same, but using O_DIRECT for output
> > > > dd2/dd2-dir - copy 2x7.6 GB in parallel from /dev/zero to local FS
> > > > dd3/dd3-dir - copy 3x5.2 GB in parallel from /dev/zero lo local FS
> > > > net1 - copy 5.2 GB from NFS3 share to local FS
> > > > mix3 - copy 3x5.2 GB from /dev/zero to local disk and two NFS3
> > > > shares
> > > > 
> > > >  I did the numbers for 2.6.19.2, 2.6.22.6 and 2.6.24-rc1. All
> > > > units are MB/sec.
> > > > 
> > > > test           2.6.19.2     2.6.22.6    2.6.24.-rc1
> > > > ----------------------------------------------------------------
> > > > dd1                  28           50             96
> > > > dd1-dir              88           88             86
> > > > dd2              2x16.5         2x11         2x44.5
> > > > dd2-dir            2x44         2x44           2x43
> > > > dd3               3x9.8        3x8.7           3x30
> > > > dd3-dir          3x29.5       3x29.5         3x28.5
> > > > net1              30-33        50-55          37-52
> > > > mix3              17/32        25/50          96/35
> > > > (disk/combined-network)
> > > 
> > > wow, really nice results!
> > 
> > Those changes seem suspiciously large to me.  I wonder if there's less
> > physical IO happening during the timed run, and correspondingly more
> > afterwards.
> > 
> 
> another option... this is ext2.. didn't the ext2 reservation stuff get
> merged into -rc1? for ext3 that gave a 4x or so speed boost (much
> better sequential allocation pattern)
> 

Yes, one would expect that to make a large difference in dd2/dd2-dir and
dd3/dd3-dir - but only on SMP.  On UP there's not enough concurrency in the
fs block allocator for any damage to occur.

Reservations won't affect dd1 though, and that went faster too.

  reply	other threads:[~2007-10-27  6:00 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-10-26 14:18 2.6.24-rc1: First impressions Martin Knoblauch
2007-10-26 15:22 ` Ingo Molnar
2007-10-26 15:29   ` Peter Zijlstra
2007-10-26 15:49     ` Rik van Riel
2007-10-26 19:21   ` Andrew Morton
2007-10-26 19:33     ` Ingo Molnar
2007-10-26 19:42       ` Andrew Morton
2007-10-27 19:14         ` Bill Davidsen
2007-10-27  5:46     ` Arjan van de Ven
2007-10-27  5:59       ` Andrew Morton [this message]
  -- strict thread matches above, loose matches on Subject: below --
2007-10-29  8:29 Martin Knoblauch
2007-10-29 11:09 Martin Knoblauch
2007-10-29 11:40 ` Ingo Molnar

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=20071026225951.db374baf.akpm@linux-foundation.org \
    --to=akpm@linux-foundation.org \
    --cc=a.p.zijlstra@chello.nl \
    --cc=arjan@infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=riel@redhat.com \
    --cc=spamtrap@knobisoft.de \
    --cc=torvalds@linux-foundation.org \
    --cc=wfg@mail.ustc.edu.cn \
    /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