Anyone, please: are the symptoms detailed above (on the previous page) to be expected when the rdirplus plus option of mount_nfs(8) is used?
Whilst I don't use NFS, the near-total emptiness seems beyond the bounds of degraded performance (see below).
If not as expected … Don, please, is this:
- something that we might feed to Apple (bug or enhancement);
- something to be fed to developers of NFS; or
- a consideration for developers of ZEVO? #zevo
References
Apple open source for NFS-73 in OS X 10.8.2
No match for NFS at lists.apple.com Mailing Lists.
From Apple's mount_nfs(8) OS X Manual Page, for the NFS-specific rdirplus option:
----
Used with NFS v3/v4 to specify that directory read operations should retrieve additional information about each entry (e.g. use the NFSv3 ReaddirPlus RPC). This option typically reduces RPC traffic for cases such as directory listings that use or display basic attributes (e.g. ``ls -F'' and ``find . -type f'' ). Note that the long directory listing format case (i.e. ``ls -l'' ) may not be helped much when the file system does not natively support extended attributes. Older implementations tended to flood the vnode and name caches with prefetched entries which may not be referenced. The current implementation avoids creating those entries until they are referenced. Try this option and see whether performance improves or degrades. Probably most useful for client to server network interconnects with a large bandwidth times delay product.
----