Linux NFS development
 help / color / mirror / Atom feed
From: Jason Holmes <jholmes@psu.edu>
To: trond.myklebust@fys.uio.no, nfs@lists.sourceforge.net
Subject: Re: 2.4 vs. 2.6 nfs client performance
Date: Thu, 13 Nov 2003 16:55:52 -0500	[thread overview]
Message-ID: <3FB3FDE8.47E819FF@psu.edu> (raw)
In-Reply-To: 3FB3924B.7450E9F7@psu.edu

Jason Holmes wrote:
> 
> Trond Myklebust wrote:
> >
> > 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.

OK, I haven't found any other program that behaves similar to Gaussian
on this, but I did do a few more runs with 2.6.0-test9-bk17 vs 2.4.22,
one set with nfs_debug on and one set with rpc_debug on.  I haven't
analyzed the files in depth (and doing so would really be beyond me at
this point), but on a "dumb" level, the nfs files are of similar length
in terms of lines, but the RPC file for 2.6.0-test9-bk17 is much larger:

[root@fs4 log]# wc -l kern.*
  16236 kern.nfs-2.4.22
  17188 kern.nfs-2.6.0-test9-bk17
  20565 kern.rpc-2.4.22
  32684 kern.rpc-2.6.0-test9-bk17

Note that there is probably some small amount of noise in these files,
but 98% of it should be from the Gaussian runs.  I put them up at:

  http://magicbus.cac.psu.edu/nfs

if you want to look at them.  One small observation is that 2.4.22
reaches much larger values of cwnd than test9-bk17, resulting in a lot
fewer calls to functions such as xprt_cwnd_limited (1861 vs. 2715). 
Whether or not this means anything, I don't know.

Trond, if none of this helps and you really want to debug this, I can
probably give you access to two machines to do so.

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

  reply	other threads:[~2003-11-13 21: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 [this message]
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=3FB3FDE8.47E819FF@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