Messages in this thread | | | Subject | Re: NFS client (10x) performance regression 2.6.14.7 -> 2.6.15 | From | Trond Myklebust <> | Date | Fri, 31 Mar 2006 10:55:20 -0500 |
| |
On Fri, 2006-03-31 at 16:35 +0200, Jakob Oestergaard wrote: > On Fri, Mar 31, 2006 at 09:21:29AM -0500, Trond Myklebust wrote: > ... > > > > Hmm... Nothing obvious. > > Ok. > > I'm wondering... Can anyone else reproduce this problem? > > Just to explain quickly: > Running nfsbench (on the NFS client) once with LEADING_EMPTY_SPACE set > to 0 and then once with the option set to 1. If there's a big change > in wall-clock execution time, this indicates that the problem exists. > > I'd be really interested in knowing whether I'm the only one who sees > this problem. > > > Try catting /proc/self/mountstats and see if the entry for your NFS > > mount shows anything interesting. > > mountstats doesn't exist on 2.6.15.7 so I can't really compare... > > I wonder if any of the following is 'interesting' :) > > device sparrow:/exported/joe mounted on /u/joe with fstype nfs statvers=1.0 > opts: rw,vers=3,rsize=32768,wsize=32768,acregmin=3,acregmax=60,acdirmin=30, > acdirmax=60,hard,intr,proto=udp,timeo=7,retrans=3 > age: 274 > caps: caps=0x1,wtmult=4096,dtsize=4096,bsize=0,namelen=255 > sec: flavor=1 > events: 175 77 3 3 14 15 108 4 0 7 0 4 0 1 2 0 0 14 0 1 4 0 0 0 0 > bytes: 194733 11746 0 0 37748 15340 13 0 > RPC iostats version: 1.0 p/v: 100003/3 (nfs) > xprt: udp 1023 0 74 74 0 74 0 > per-op statistics > ... then follows the nfsstat numbers as far as I can see ...
No. They are the nfsstat numbers + timing information. I was interested in seeing if the latter can show up something.
Cheers Trond
- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |