NFS outperforms PVFS for application XXX. Why?
In an environment where there is one client accessing a file on one server, NFS will outperform PVFS in many benchmarks. NFS has completely different consistency semantics, which work very well when just one process accesses a file. There is some ongoing work that will optionally offer similar consistency semantics for PVFS, at which point we will be playing on a level field, so to speak. However, if you insist on benchmarking PVFS and NFS in a single-client test, there are some immediate adjustments you can make. The easiest way to improve PVFS performance is to increase the block size of each access. Large block sizes help most file systems, but for PVFS they make a much larger difference in performance than they do for other file systems. Also, if the TroveSyncMeta and TroveSyncData options are set to no in your PVFS configuration file, the server will sync data to disk only when a flush or close operation is called. The TroveSyncMeta option is set to yes by default, to limit the am
