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 09:21:29 -0500 |
| |
On Fri, 2006-03-31 at 16:08 +0200, Jakob Oestergaard wrote: > On Fri, Mar 31, 2006 at 08:44:18AM -0500, Trond Myklebust wrote: > ... > > Just apply > > http://client.linux-nfs.org/Linux-2.6.x/2.6.16/linux-2.6.16-NFS_ALL.dif > > > > to a clean 2.6.16. > > Done. Plain 2.6.16 plus the patch. > > --------------------------------------- > [puffin:joe] $ time ./nfsbench > > real 0m29.581s > user 0m0.000s > sys 0m0.208s > [puffin:joe] $ nfsstat > Client rpc stats: > calls retrans authrefrsh > 13222 0 0 > > <snip v2> > > Client nfs v3: > null getattr setattr lookup access readlink > 0 0% 2577 19% 1 0% 24 0% 18 0% 0 0% > read write create mkdir symlink mknod > 7045 53% 3200 24% 0 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% > > --------------------------------------- > > Lots of getattr and lots of read... > > I verified that the patch really got applied. > > What could the difference be? > > I've attached my .config - if there is anything in there you think might > have an impact, please let me know - again, I can try anything on this > machine...
Hmm... Nothing obvious.
Try catting /proc/self/mountstats and see if the entry for your NFS mount shows anything interesting.
Cheers, Trond
> ... > > Linux servers do not yet support anything larger than a 32k r/wsize (and > > in any case, you would have to switch towards using TCP). My home > > directory is on a filer. > > Ok. >
- 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/
| |