From: Martin Knoblauch <knobi@knobisoft.de>
To: Ingo Molnar <mingo@elte.hu>, Andrew Morton <akpm@linux-foundation.org>
Cc: 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: Mon, 29 Oct 2007 04:09:56 -0700 (PDT) [thread overview]
Message-ID: <213736.67377.qm@web32614.mail.mud.yahoo.com> (raw)
----- Original Message ----
> From: Ingo Molnar <mingo@elte.hu>
> To: Andrew Morton <akpm@linux-foundation.org>
> Cc: 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
> Sent: Friday, October 26, 2007 9:33:40 PM
> Subject: Re: 2.6.24-rc1: First impressions
>
>
> * Andrew Morton 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.
>
> so a final 'sync' should be added to the test too, and the time
> it
>
takes
> factored into the bandwidth numbers?
>
One of the reasons I do 15 GB transfers is to make sure that I am well above the possible page cache size. And of course I am doing a final sync to finish the runs :-) The sync is also running faster in 2.6.24-rc1.
If I factor it in the results for dd1/dd3 are:
test 2.6.19.2 2.6.22.6 2.6.24-rc1
sync time 18sec 19sec 6sec
dd1 27.5 47.5 92
dd3 3x9.1 3x8.5 3x29
So basically including the sync time make 2.6.24-rc1 even more promosing. Now, I know that my benchmarks numbers are crude and show only a very small aspect of system performance. But - it is an aspect I care about a lot. And those benchmarks match my use-case pretty good.
Cheers
Martin
next reply other threads:[~2007-10-29 11:10 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-29 11:09 Martin Knoblauch [this message]
2007-10-29 11:40 ` 2.6.24-rc1: First impressions Ingo Molnar
-- strict thread matches above, loose matches on Subject: below --
2007-10-29 8:29 Martin Knoblauch
2007-10-26 14:18 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
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=213736.67377.qm@web32614.mail.mud.yahoo.com \
--to=knobi@knobisoft.de \
--cc=a.p.zijlstra@chello.nl \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=riel@redhat.com \
--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 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.