Bug 1610658

Summary: CPU clocking to 1900% during directory operations
Product: [Red Hat Storage] Red Hat Gluster Storage Reporter: Karan Sandha <ksandha>
Component: coreAssignee: Mohit Agrawal <moagrawa>
Status: CLOSED NOTABUG QA Contact: Rahul Hinduja <rhinduja>
Severity: high Docs Contact:
Priority: medium    
Version: rhgs-3.4CC: amukherj, atumball, ksandha, ravishankar, rgowdapp, rhs-bugs, sankarshan, sheggodu, storage-qa-internal
Target Milestone: ---Keywords: Performance, ZStream
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2019-04-24 17:38:49 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:

Comment 10 Raghavendra G 2018-09-10 06:06:34 UTC 
From what I observed on bricks, CPU utilization of a single multiplexed brick process is equal to the sum of CPU utilizations of all brick processes if they are not multiplexed. From that perspective this may not be a bug at all. I think we need to first prove that this high cpu utilization is actually bringing down the performance. Only then this can be considered as a bug, otherwise it may not.
Comment 11 Mohit Agrawal 2018-09-10 06:26:25 UTC 
I agree with raghu, on the basis of showing high CPU utilization only we can't say it is a bug.

I think on the basis top CPU Usage only we can't say it is correct CPU usage for glusterfsd.

I think to measure correct CPU usage we should use perf command

As we can see below Brendan Article "CPU utilization is wrong " 
http://www.brendangregg.com/blog/2017-05-09/cpu-utilization-is-wrong.html

Can you please run the same and share the result??

Thanks,
Mohit Agrawal
Comment 14 Amar Tumballi 2019-04-24 17:38:49 UTC 
Closing this as NOTABUG, with details in comment#10, comment#11, comment#12

Please reopen if the high CPU usage is seen even when there are no scale of volumes.
Comment 15 Red Hat Bugzilla 2023-09-14 04:32:28 UTC 
The needinfo request[s] on this closed bug have been removed as they have been unresolved for 1000 days