Readdir ls -f graphs

From Linux NFS

Revision as of 17:29, 7 April 2011 (view source) Amschuma (Talk | contribs) ← Older edit		Revision as of 17:31, 7 April 2011 (view source) Amschuma (Talk | contribs) (→NFS v3) Newer edit →
Line 28:		Line 28:
	=== NFS v3 ===		=== NFS v3 ===
	* [[File:v3_ls_f_noplus_rpc.jpg]]		* [[File:v3_ls_f_noplus_rpc.jpg]]
		+	** 2.6.36 kernels issue fewer RPC operations than 2.6.38 kernels
	* [[File:v3_ls_f_plus_rpc.jpg]]		* [[File:v3_ls_f_plus_rpc.jpg]]
		+
	=== NFS v4 ===		=== NFS v4 ===
	* [[File:v4_ls_f_noplus_rpc.jpg]]		* [[File:v4_ls_f_noplus_rpc.jpg]]
	* [[File:v4_ls_f_plus_rpc.jpg]]		* [[File:v4_ls_f_plus_rpc.jpg]]

---

Revision as of 17:31, 7 April 2011

    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 1 Real 1.1 NFS v3 1.2 NFS v4 2 Sys 2.1 NFS v3 2.2 NFS v4 3 RPC ops 3.1 NFS v3 3.2 NFS v4

Real

NFS v3

• 
• 
  • 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

• 
• 

Sys

NFS v3

• 
• 

NFS v4

• 
• 
  • Unmodified 2.6.38 gives the worst performance here. All other kernels seem to give roughly the same results.

RPC ops

NFS v3

• 
  • 2.6.36 kernels issue fewer RPC operations than 2.6.38 kernels
• 

NFS v4

• 
•