Readdir ls -f graphs

From Linux NFS

Revision as of 17:45, 7 April 2011 by Amschuma (Talk | contribs)
Jump to: navigation, search
    36: Linux 2.6.36
36NORC: Linux 2.6.36 (without readdir cap)
    38: Linux 2.6.38
  38RC: Linux 2.6.38 (with readdir cap added back)
  38NB: Linux 2.6.38 (with Neil Brown's patch and loop detection)

Contents

Real

NFS v3

  • V3 ls f noplus real.jpg
  • V3 ls f plus real.jpg
    • 2.6.38 performs the same as 2.6.36 with the readdir plus cap removed. Using readdir rather than readdir plus is faster in this case.

NFS v4

  • V4 ls f noplus real.jpg
  • V4 ls f plus real.jpg

Sys

NFS v3

  • V3 ls f noplus sys.jpg
  • V3 ls f plus sys.jpg

NFS v4

  • V4 ls f noplus sys.jpg
  • V4 ls f plus sys.jpg
    • Unmodified 2.6.38 gives the worst performance here. All other kernels seem to give roughly the same results.

RPC ops

NFS v3

  • V3 ls f noplus rpc.jpg
    • 2.6.36 kernels issue fewer RPC operations than 2.6.38 kernels
  • V3 ls f plus rpc.jpg
    • Kernels with readdir plus limiting seem to have fewer RPC operations than kernels without the limit.

NFS v4

  • V4 ls f noplus rpc.jpg
    • 2.6.36 based kernels issue fewer RPC calls than 2.6.38 kernels.
  • V4 ls f plus rpc.jpg
    • 2.6.36 based kernels give the fewest number of RPC calls. 2.6.38 with readdir plus limiting issues a few hundred more RPC operations, but not nearly as much as an unmodified 2.6.38 kernel.
Personal tools