All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jakob Oestergaard <jakob@unthought.net>
To: Trond Myklebust <trond.myklebust@fys.uio.no>
Cc: linux-kernel@vger.kernel.org
Subject: Re: NFS client (10x) performance regression 2.6.14.7 -> 2.6.15
Date: Fri, 31 Mar 2006 14:45:19 +0200	[thread overview]
Message-ID: <20060331124518.GH9811@unthought.net> (raw)
In-Reply-To: <1143807770.8096.4.camel@lade.trondhjem.org>

On Fri, Mar 31, 2006 at 07:22:50AM -0500, Trond Myklebust wrote:
...
> 
> Some nfsstat output comparing the good and bad cases would help.

Clean boot on 2.6.15 and 2.6.14.7, one run of nfsbench with
LEADING_EMPTY_SPACE=1.  I've skipped the NFS v2 stats because they're
all 0.

--- Run on bad kernel ---

[puffin:joe] $ uname -a
Linux puffin 2.6.15 #1 SMP Fri Mar 31 11:10:28 CEST 2006 i686 GNU/Linux
[puffin:joe] $ nfsstat 
Client rpc stats:
calls      retrans    authrefrsh
63         0          0       

<snip v2 stats>

Client nfs v3:
null       getattr    setattr    lookup     access     readlink   
0       0% 11     18% 0       0% 26     42% 14     22% 0       0% 
read       write      create     mkdir      symlink    mknod      
4       6% 0       0% 0       0% 0       0% 0       0% 0       0% 
remove     rmdir      rename     link       readdir    readdirplus
0       0% 0       0% 0       0% 0       0% 0       0% 4       6% 
fsstat     fsinfo     pathconf   commit     
0       0% 2       3% 0       0% 0       0% 
[puffin:joe] $ time ./nfsbench 

real    0m29.242s
user    0m0.000s
sys     0m0.160s
[puffin:joe] $ nfsstat 
Client rpc stats:
calls      retrans    authrefrsh
13240      0          0       

<snip v2 stats>

Client nfs v3:
null       getattr    setattr    lookup     access     readlink   
0       0% 2583   19% 0       0% 30      0% 24      0% 0       0% 
read       write      create     mkdir      symlink    mknod      
7045   53% 3200   24% 1       0% 0       0% 0       0% 0       0% 
remove     rmdir      rename     link       readdir    readdirplus
0       0% 0       0% 0       0% 0       0% 0       0% 34      0% 
fsstat     fsinfo     pathconf   commit     
0       0% 2       0% 0       0% 319     2% 

[puffin:joe] $

--- Run on good kernel ---

[puffin:joe] $ uname -a
Linux puffin 2.6.14.7 #1 SMP Fri Mar 31 10:41:59 CEST 2006 i686
GNU/Linux
[puffin:joe] $ nfsstat 
Client rpc stats:
calls      retrans    authrefrsh
52         0          0       

<snip v2 stats>

Client nfs v3:
null       getattr    setattr    lookup     access     readlink   
0       0% 7      14% 0       0% 24     48% 13     26% 0       0% 
read       write      create     mkdir      symlink    mknod      
4       8% 0       0% 0       0% 0       0% 0       0% 0       0% 
remove     rmdir      rename     link       readdir    readdirplus
0       0% 0       0% 0       0% 0       0% 0       0% 0       0% 
fsstat     fsinfo     pathconf   commit     
0       0% 2       4% 0       0% 0       0% 

[puffin:joe] $ time ./nfsbench 

real    0m0.224s
user    0m0.000s
sys     0m0.072s
[puffin:joe] $ nfsstat 
Client rpc stats:
calls      retrans    authrefrsh
384        0          0       

<snip v2 stats>

Client nfs v3:
null       getattr    setattr    lookup     access     readlink   
0       0% 10      2% 1       0% 26      6% 15      3% 0       0% 
read       write      create     mkdir      symlink    mknod      
6       1% 321    84% 0       0% 0       0% 0       0% 0       0% 
remove     rmdir      rename     link       readdir    readdirplus
0       0% 0       0% 0       0% 0       0% 0       0% 0       0% 
fsstat     fsinfo     pathconf   commit     
0       0% 2       0% 0       0% 1       0% 

[puffin:joe] $


-- 

 / jakob


  reply	other threads:[~2006-03-31 12:45 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-03-31  9:48 NFS client (10x) performance regression 2.6.14.7 -> 2.6.15 Jakob Oestergaard
2006-03-31 11:22 ` NFS client regression, simple test program Jakob Oestergaard
2006-03-31 12:22 ` NFS client (10x) performance regression 2.6.14.7 -> 2.6.15 Trond Myklebust
2006-03-31 12:45   ` Jakob Oestergaard [this message]
2006-03-31 13:06     ` Trond Myklebust
2006-03-31 13:21       ` Jakob Oestergaard
2006-03-31 13:44         ` Trond Myklebust
2006-03-31 14:08           ` Jakob Oestergaard
2006-03-31 14:21             ` Trond Myklebust
2006-03-31 14:35               ` Jakob Oestergaard
2006-03-31 14:49                 ` Bill Rugolsky Jr.
2006-03-31 14:57                   ` Jakob Oestergaard
2006-03-31 15:04                     ` Bill Rugolsky Jr.
2006-03-31 15:24                       ` Jakob Oestergaard
2006-03-31 16:35                         ` Bill Rugolsky Jr.
2006-03-31 18:52                           ` Jakob Oestergaard
2006-03-31 15:55                 ` Trond Myklebust
2006-03-31 16:04                   ` Jakob Oestergaard
2006-04-03 15:26                     ` Jakob Oestergaard
2006-04-03 15:41                       ` Trond Myklebust
2006-04-03 15:45                         ` Jakob Oestergaard
2006-04-04  9:22                           ` Jakob Oestergaard
2006-04-24 22:03                             ` Trond Myklebust
2006-04-25  8:08                               ` Jakob Oestergaard

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=20060331124518.GH9811@unthought.net \
    --to=jakob@unthought.net \
    --cc=linux-kernel@vger.kernel.org \
    --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.