From: Eric Whiting <ewhiting@amis.com>
To: trond.myklebust@fys.uio.no
Cc: Jason Holmes <jholmes@psu.edu>, nfs@lists.sourceforge.net
Subject: Re: 2.4 vs. 2.6 nfs client performance
Date: Thu, 13 Nov 2003 08:56:15 -0700 [thread overview]
Message-ID: <3FB3A99F.126920E7@amis.com> (raw)
In-Reply-To: 16306.59249.857512.354675@charged.uio.no
Trond Myklebust wrote:
> Any hints on how I can reproduce your results?
Trond,
This is not the same test, nor the same results as Jason's, but here is some
more data from bonnie and dd tests.This shows some write performance difference
between 2.4 and 2.6
eric
SERVER: 2.4.21
CLIENT: 2.4.19 nfsv3
Bonnie
Writing with putc()... done: 9132 kB/s 33.4 %CPU
Rewriting... done: 8713 kB/s 4.2 %CPU
Writing intelligently...done: 9116 kB/s 4.6 %CPU
$ rm file;time dd if=/dev/zero of=file bs=1 count=10000000
10000000+0 records in
10000000+0 records out
real 0m30.404s
user 0m3.930s
sys 0m26.250s
CLIENT: 2.6.0-test6-mm4
Writing with putc()... done: 806 kB/s 5.4 %CPU
Rewriting... done: 3321 kB/s 3.9 %CPU
Writing intelligently...done: 2715 kB/s 2.4 %CPU
$ rm file;time dd if=/dev/zero of=file bs=1 count=10000000
10000000+0 records in
10000000+0 records out
real 1m37.848s
user 0m17.355s
sys 1m8.947s
-------------------------------------------------------
This SF.Net email sponsored by: ApacheCon 2003,
16-19 November in Las Vegas. Learn firsthand the latest
developments in Apache, PHP, Perl, XML, Java, MySQL,
WebDAV, and more! http://www.apachecon.com/
_______________________________________________
NFS maillist - NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs
next prev parent reply other threads:[~2003-11-13 15:55 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-11-12 18:05 2.4 vs. 2.6 nfs client performance Jason Holmes
2003-11-12 20:20 ` Trond Myklebust
2003-11-12 20:51 ` Jason Holmes
2003-11-12 21:18 ` Trond Myklebust
2003-11-12 21:33 ` Jason Holmes
2003-11-12 23:22 ` Trond Myklebust
2003-11-13 1:20 ` Jason Holmes
2003-11-13 2:07 ` Trond Myklebust
2003-11-13 14:16 ` Jason Holmes
2003-11-13 21:55 ` Jason Holmes
2003-11-14 0:22 ` Trond Myklebust
2003-11-14 18:37 ` Jason Holmes
2003-11-14 21:11 ` Trond Myklebust
2003-11-16 15:54 ` Jason Holmes
2003-11-13 15:56 ` Eric Whiting [this message]
2003-11-13 17:55 ` Trond Myklebust
2003-11-13 18:59 ` Eric Whiting
2003-11-13 19:09 ` Eric Whiting
2003-11-13 19:28 ` Trond Myklebust
2003-11-13 19:18 ` Jason Holmes
2003-11-12 22:08 ` Eric Whiting
-- strict thread matches above, loose matches on Subject: below --
2003-11-13 19:42 Duc Vianney
2003-11-13 20:02 ` Trond Myklebust
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=3FB3A99F.126920E7@amis.com \
--to=ewhiting@amis.com \
--cc=jholmes@psu.edu \
--cc=nfs@lists.sourceforge.net \
--cc=trond.myklebust@fys.uio.no \
/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.