Bug 790333

Summary:	Remove performance translators in the NFS server stack
Product:	[Red Hat Storage] Red Hat Gluster Storage	Reporter:	Krishna Srinivas <ksriniva>
Component:	glusterfs	Assignee:	Ric Wheeler <rwheeler>
Status:	CLOSED CURRENTRELEASE	QA Contact:	Anush Shetty <ashetty>
Severity:	medium	Docs Contact:
Priority:	high
Version:	1.0	CC:	gluster-bugs, jdarcy, rwheeler, sdharane, vbellur
Target Milestone:	---
Target Release:	---
Hardware:	All
OS:	All
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2015-08-10 07:47:34 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:
Bug Blocks:	817967

Description Krishna Srinivas 2012-02-14 09:47:29 UTC

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.

Comment 1 Vijay Bellur 2012-02-14 10:32:35 UTC

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.

Comment 2 Krishna Srinivas 2012-02-15 07:30:46 UTC

I agree, 3.3 would be a good release to make this decision.

Comment 3 Amar Tumballi 2012-03-06 06:27:59 UTC

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?

Comment 4 Krishna Srinivas 2012-03-06 07:16:34 UTC

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.

Comment 5 Anand Avati 2012-03-18 08:12:53 UTC

CHANGE: http://review.gluster.com/2883 (volgen: by default don't include performance xlators in nfs volfile) merged in master by Anand Avati (avati)

Comment 6 Anush Shetty 2012-05-22 04:59:48 UTC

Verified with 3.3.0qa42.