cloudstack-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From jayakarteek <>
Subject [GitHub] cloudstack issue #1918: Management Server UI (VM statistics page) CPU Utiliz...
Date Tue, 14 Feb 2017 05:46:31 GMT
Github user jayakarteek commented on the issue:
    HI  raferweingartner, nvazquez<>,
    Yes as specified in mail,
    The issue is specific to VMware.
    From: Nicolas Vazquez []
    Sent: Tuesday, February 14, 2017 5:36 AM
    To: apache/cloudstack <>
    Cc: Jayakarteek Vasana <>; Mention <>
    Subject: Re: [apache/cloudstack] Management Server UI (VM statistics page) CPU Utilized
value is incorrect. (#1918)
    Hi @jayakarteek<> @rafaelweingartner<>,
    I confirm issue, I tested using an instance with 1 CPU 500Mhz. I'll add screenshots for
cases when CPU utilization is low and high:
    First, with little utilization, vSphere shows 51Mhz CPU Utilization, while on Management
Server statistics shows 51% CPU utilization
    Then, ran a loop to increase CPU utilization increasing it to ~1609Mhz and Management
Server statistics shows 1609% CPU Utilization,
    Hope this helps!
    You are receiving this because you were mentioned.
    Reply to this email directly, view it on GitHub<>,
or mute the thread<>.
    This e-mail may contain privileged and confidential information which is the property
of Accelerite, a Persistent Systems business. It is intended only for the use of the individual
or entity to which it is addressed. If you are not the intended recipient, you are not authorized
to read, retain, copy, print, distribute or use this message. If you have received this communication
in error, please notify the sender and delete all copies of this message. Accelerite, a Persistent
Systems business does not accept any liability for virus infected mails.

If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at or file a JIRA ticket
with INFRA.

View raw message