Description of problem: Performance translators in the NFS server do not provide any advantage as NFS client takes care of all the performance needs. Hence removing the performance translators from the NFS server stack will mean having lesser variables in the storage environment and more stability.
Before we go about doing this, it would be better to run tests with performance translators enabled & disabled in our performance setup. Only when we have the data let us bring about this change.
I agree, 3.3 would be a good release to make this decision.
I think we should do it anyways ASAP, as I see that in many cases NFS sends open with GF_OPEN_NOWB flag (on wbflags arg), which makes the translator a pass through. So don't see much use on this anyways. Avati/Vijay, any thoughts on this?
Actually with anon-fd changes the writebehind is not getting disabled for writes anymore. I think this was the reason we saw write performance drop (with perf xlators 'dd' gave 75 MBps and without perf xlators it gave 100MBps on gige). Also write-behind was never getting used before anon-fd changes.
CHANGE: http://review.gluster.com/2883 (volgen: by default don't include performance xlators in nfs volfile) merged in master by Anand Avati (avati)
Verified with 3.3.0qa42.