Bug 1710371

Summary:	Minor improvements across codebase for performance gain
Product:	[Community] GlusterFS	Reporter:	Amar Tumballi <atumball>
Component:	core	Assignee:	bugs <bugs>
Status:	CLOSED UPSTREAM	QA Contact:
Severity:	high	Docs Contact:
Priority:	high
Version:	mainline	CC:	bugs, pasik
Target Milestone:	---	Keywords:	Performance, Tracking
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2020-03-12 14:29: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:

Description Amar Tumballi 2019-05-15 12:43:00 UTC

Description of problem:
There are many places in glusterfs code, where we can do minor improvements to handle CPU cycles better.

* No need for memset().
* Initializing large array!
* revisit locked regions, and see if it can be optimized.
* Reduce call to library functions, instead  cache some results.
* other such minor improvements, which would help overall performance.

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


Expected results:
With focus on such improvement, we expect better CPU utilization, which means better performance in the long run.

Additional info:
This bug can be a tracker bug, and hence this shouldn't be closed as long as we feel we have good performance.

Comment 1 Worker Ant 2019-05-15 12:47:50 UTC

REVIEW: https://review.gluster.org/22242 (inode: reduce inode-path execution time) posted (#3) for review on master by Amar Tumballi

Comment 2 Worker Ant 2020-03-12 14:29:59 UTC

This bug is moved to https://github.com/gluster/glusterfs/issues/1053, and will be tracked there from now on. Visit GitHub issues URL for further details