Robert Heller wrote:
Seems odd that caching wouldn't just happen naturally in the nfs client.
I am not sure if it even makes sense to cache NFS files on a nfs client -- how does the client know that the file might not have changed on the server? At the very least it has to check the file mod times on the server to be sure its local cache is valid.
Pretty much all filesytems cache, and would be unusably slow if they didn't. File attributes should be only a few seconds on NFS, but that should be enough to avoid killing your server.
Maybe it is updating the access time on each read or something that causes the activity.
It is either re-reading the files or checking mod times to determin if the local cached copy is valid. Either way, lots of traffic.
And this was hundreds of ops/second?