Bug 1631886

Summary:	Update database profile settings for gluster
Product:	[Community] GlusterFS	Reporter:	Xavi Hernandez <jahernan>
Component:	cli	Assignee:	Xavi Hernandez <jahernan>
Status:	CLOSED CURRENTRELEASE	QA Contact:
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	mainline	CC:	bugs
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	glusterfs-6.0	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:
Clones:	1644120 (view as bug list)		Environment:
Last Closed:	2019-03-25 16:30:59 UTC	Type:	Bug
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:	1644120

Description Xavi Hernandez 2018-09-21 19:51:09 UTC

Description of problem:

Database performance on gluster can be improved by enabling some additional options:

client-io-threads=on
open-behind=on
read-after-open=yes
server.event-threads=4
client.event-threads=4

The db profile group needs to be updated.

Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:

Comment 1 Worker Ant 2018-09-21 19:55:24 UTC

REVIEW: https://review.gluster.org/21247 (Update database profile group) posted (#1) for review on master by Xavi Hernandez

Comment 2 Worker Ant 2018-09-24 17:56:18 UTC

COMMIT: https://review.gluster.org/21247 committed in master by "Amar Tumballi" <amarts> with a commit message- Update database profile group

Some performance testing has revealed that pgbench performs 3x better
when these options are set:

performance.client-io-threads=on
performance.open-behind=on
performance.read-after-open=yes
server.event-threads=4
client.event-threads=4

Change-Id: I36ce389f893a8af13aac5f8285104d749b73d098
fixes: bz#1631886
Signed-off-by: Xavi Hernandez <xhernandez>

Comment 3 Shyamsundar 2019-03-25 16:30:59 UTC

This bug is getting closed because a release has been made available that should address the reported issue. In case the problem is still not fixed with glusterfs-6.0, please open a new bug report.

glusterfs-6.0 has been announced on the Gluster mailinglists [1], packages for several distributions should become available in the near future. Keep an eye on the Gluster Users mailinglist [2] and the update infrastructure for your distribution.

[1] https://lists.gluster.org/pipermail/announce/2019-March/000120.html
[2] https://www.gluster.org/pipermail/gluster-users/