Bug 1340159 - High CPU utilisation on RHS-C deployed cluster
Summary: High CPU utilisation on RHS-C deployed cluster
Keywords:
Status: CLOSED WORKSFORME
Alias: None
Product: Red Hat Storage Console
Classification: Red Hat Storage
Component: core
Version: 2
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
: 2
Assignee: anmol babu
QA Contact: sds-qe-bugs
URL:
Whiteboard:
Depends On:
Blocks: Console-2-DevFreeze
TreeView+ depends on / blocked
 
Reported: 2016-05-26 14:42 UTC by Chris Blum
Modified: 2016-07-18 16:11 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-06-16 13:01:05 UTC
Embargoed:

Attachments (Terms of Use)
CPU usage in libvirt (18.54 KB, image/jpeg)
2016-05-26 15:21 UTC, Chris Blum 		no flags Details
View All

Description Chris Blum 2016-05-26 14:42:25 UTC 
Description of problem:
After deploying a RHS-C Ceph cluster, the CPU utilisation of the VMs is very high. This seems to be connected to salt provisioning running every second. Since the CPU utilisation is very high, this can influence the overall ceph performance and cause other issues when Ceph wants to recover.
https://www.dropbox.com/s/aso9c9utwq0cz2n/Screenshot%202016-05-26%2016.27.59.jpg?dl=0

Version-Release number of selected component (if applicable):
Latest
Comment 2 Chris Blum 2016-05-26 15:21:42 UTC 
Created attachment 1162052 [details]
CPU usage in libvirt

Copy of screenshot from dropbox URL
Comment 3 Nishanth Thomas 2016-06-06 16:04:25 UTC 
Not seeing the hight utilization at the moment. Need to check over the time how it behaves in a stress setup
Comment 4 Chris Blum 2016-06-06 16:27:14 UTC 
how much utilization do you see in your boxes? For me it usually fills up 1 CPU core - which might not be much depending on the installation
Comment 5 Nishanth Thomas 2016-06-14 13:21:38 UTC 
On all my boxes 2-3% utilization over a period time. I am using the latest build. Could you please try and let me know?
Comment 6 Nishanth Thomas 2016-06-16 13:01:05 UTC 
Closing this bug as this bug is not seen on the latest builds
Note You need to log in before you can comment on or make changes to this bug.