From: Jason Holmes <jholmes@psu.edu>
To: trond.myklebust@fys.uio.no
Cc: nfs@lists.sourceforge.net
Subject: Re: 2.4 vs. 2.6 nfs client performance
Date: Sun, 16 Nov 2003 10:54:23 -0500 [thread overview]
Message-ID: <3FB79DAF.8E483BD5@psu.edu> (raw)
In-Reply-To: 16309.17670.931812.401791@charged.uio.no
Trond Myklebust wrote:
>
> >>>>> " " == Jason Holmes <jholmes@psu.edu> writes:
>
> > Files should be up there (http://magicbus.cac.psu.edu/nfs). I
> > do have to admit that something odd is going on - 2.4.22 still
> > is faster than 2.6.0-test9-bk17 and test9-bk17 is still showing
> > the large amount of commits, but both of them are running
> > faster than they did before on the sync mounts and I'm not sure
> > what I might have changed to cause this.
>
> Hmm... It looks like you are doing a succession of 4k commits. I'll
> bet the read() code is involved in this...
>
> Could you try the following patch and see if it improves things?
That made a huge difference:
Client nfs v3:
null getattr setattr lookup access readlink
0 0% 714 0% 0 0% 110 0% 204 0% 0 0%
read write create mkdir symlink mknod
873 0% 178571 92% 24 0% 0 0% 0 0% 0 0%
remove rmdir rename link readdir readdirplus
24 0% 0 0% 0 0% 0 0% 18 0% 0 0%
fsstat fsinfo pathconf commit
0 0% 3 0% 0 0% 13175 6%
Client rpc stats:
calls retrans authrefrsh
193716 13 0
It also cut the job time in about half. I put a level9 log of it up
with the other ones. I'll have to rerun the 2.4 vs. this, but I think
that this change makes the 2.6 client faster than the 2.4 for this case.
Thanks,
--
Jason Holmes
-------------------------------------------------------
This SF. Net email is sponsored by: GoToMyPC
GoToMyPC is the fast, easy and secure way to access your computer from
any Web browser or wireless device. Click here to Try it Free!
https://www.gotomypc.com/tr/OSDN/AW/Q4_2003/t/g22lp?Target=mm/g22lp.tmpl
_______________________________________________
NFS maillist - NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs
next prev parent reply other threads:[~2003-11-16 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 [this message]
2003-11-13 15:56 ` Eric Whiting
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=3FB79DAF.8E483BD5@psu.edu \
--to=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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox