Bug 1710371 - Minor improvements across codebase for performance gain
Summary: Minor improvements across codebase for performance gain
Keywords:
Status: CLOSED UPSTREAM
Alias: None
Product: GlusterFS
Classification: Community
Component: core
Version: mainline
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: ---
Assignee: bugs@gluster.org
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-05-15 12:43 UTC by Amar Tumballi
Modified: 2020-03-12 14:29 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2020-03-12 14:29:59 UTC
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Gluster.org Gerrit 22242 0 None Abandoned inode: reduce inode-path execution time 2019-08-14 19:30:32 UTC

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


Note You need to log in before you can comment on or make changes to this bug.