Github user rafaelweingartner commented on the issue:

    https://github.com/apache/cloudstack/pull/1918
  
    @nvazquez, this helped.
    
    I checked the “VmwareResource.java” at line 5113 is obtained the CPU 
usage of VM. From @jayakarteek explanations I understood that the usage does 
not come as %; VMware systems show the value as a continuous value of CPU used 
in MHz.  Does not the object “objProps” (created at line 5092) contain the 
configured CPU for the VM? So, the proper conversion could be applied on 
“VmwareResource.java” at line 5186, making the POJO (VmStatsEntry) 
consistent; otherwise, there is a variable called “cpuUtilization” that 
gives the idea of percentage/ratio of usage, but in reality, it is carrying the 
real used valued of CPU in MHz.
    
    I also understood the issue regarding the CPU cap, but do not you think 
that if users select a service offering of 500MHz and their VMs are consuming 
1GHz, it would be interesting to show that the VM is using more than they would 
expect? The cloud provider is being very generous in this case :)


---
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 infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

Reply via email to