How can I achieve low latency for NFS exports in order to e.g. have developers work nicely in Eclipse/Visual Studio with their workspaces mounted over NFS?
How can I achieve low latency for NFS exports in order to e.g. have developers work nicely in Eclipse/Visual Studio with their workspaces mounted over NFS?
This sounds like you're still in the design stage. If that's true, a few things to look at are:
There's a good NFS FAQ, including some tuning tips, over yonder: http://nfs.sourceforge.net/
Don't compile over NFS. NFS performance is usually a factor of the disk I/O performance and compiling is what's going to drive your number of file I/O ops.
If you can't avoid that, caching is what will save the day. Cram that NFS server as full of RAM as you can, use asynchronous writes and enable all caching you can client-side. The fact is that a RAID is no better at handling (non-cached) disk operations then a single hard disk. And with the small file sizes of a compilation workload, combined throughput won't change a thing.
Wait for filesystem caching, or don't do compiles over NFS. Hard disks are always going to be quicker than network filesystems.
Put the files on a very fast disk or a built-for-speed RAID array since disk IO will determine the lower bound on your latency whether the client is local or remote. The other answers are also OK.
A nice solution is to make the file server be a build server also.