The v3 metadata problem is common knowledge
V3 metadata reads can spoil even a small network (not just enterprise).
Classic example - firefox/thunderbird. These two pieces of software becomes a network DOS tool if the users $HOME is on NFS v3. They use SQL-lite (which is increasingly popular with many other developers as well) to maintain most of the cache, history, etc. The result is that even one user on a 1Gbit network can produce a rate of metadata requests that is enough to choke a rather reasonable NFS server to a point where you cannot read a basic DVD SD movie off it without interruptions.
"Accelerating" such metadata does not fix the fundamental problem with v3. The more apps use embedded databases like SQL-lite the worse it will get and as long as it is v3 there will be more and more requests for metadata to filers.
The real solution to this is NFSv4 which allows caching some of this metadata locally and telling the server that it has been cached (something SMB/CIFS has been doing for 10+ years now).