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: Thu, 13 Nov 2003 09:16:43 -0500 [thread overview]
Message-ID: <3FB3924B.7450E9F7@psu.edu> (raw)
In-Reply-To: 16306.59249.857512.354675@charged.uio.no
Trond Myklebust wrote:
>
> >>>>> " " == Jason Holmes <jholmes@psu.edu> writes:
>
> > FWIW, I ran the test with nfsvers=2 (with the export still
> > being async) and it finished in 112.53user 45.02system
> > 2:43.50elapsed 96%CPU.
>
> For comparison, on my own machine, I get stats of the form:
>
> Client rpc stats:
> calls retrans authrefrsh
> 248291 6225 0
> Client nfs v2:
> null getattr setattr root lookup readlink
> 0 0% 0 0% 0 0% 0 0% 0 0% 0 0%
> read wrcache write create remove rename
> 0 0% 0 0% 0 0% 0 0% 0 0% 0 0%
> link symlink mkdir rmdir readdir fsstat
> 0 0% 0 0% 0 0% 0 0% 0 0% 0 0%
>
> Client nfs v3:
> null getattr setattr lookup access readlink
> 0 0% 77 0% 0 0% 60 0% 94 0% 0 0%
> read write create mkdir symlink mknod
> 0 0% 240378 96% 8 0% 0 0% 0 0% 0 0%
> remove rmdir rename link readdir readdirplus
> 33 0% 0 0% 0 0% 0 0% 0 0% 12 0%
> fsstat fsinfo pathconf commit
> 0 0% 1 0% 0 0% 7628 3%
>
> Any hints on how I can reproduce your results?
Unfortunately Gaussian's licensing would prohibit me from passing it
along to reproduce this. I'll try to reproduce this with another
program this morning and get back to you.
Thanks,
--
Jason Holmes
-------------------------------------------------------
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 14:16 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 [this message]
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
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=3FB3924B.7450E9F7@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 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.