cloudstack-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Andrija Panic (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CLOUDSTACK-9226) Wrong number of sockets reported
Date Thu, 03 Nov 2016 10:07:58 GMT

    [ https://issues.apache.org/jira/browse/CLOUDSTACK-9226?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15632278#comment-15632278
] 

Andrija Panic commented on CLOUDSTACK-9226:
-------------------------------------------

Im not sure if this is the right place (I dont see other ticket for this) - on my host with
E5-2650 v2 CPUs (native 2.6GHz, turbobust up to 3.4 GHz) - cloudstack reports 32 cores with
3.4 GHz speeds - and this effectively does over-provisioning of CPU (ACS think we have 32x3.4GHz,
but in reality we have only 32x2.6GHz)

Any info on this, this is killing performance for some hosts, that are near CPU limit... (we
use KVM here, ACS 4.8, but same on 4.5)

Thanks,
Andrija

> Wrong number of sockets reported
> --------------------------------
>
>                 Key: CLOUDSTACK-9226
>                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9226
>             Project: CloudStack
>          Issue Type: Bug
>      Security Level: Public(Anyone can view this level - this is the default.) 
>          Components: KVM
>    Affects Versions: 4.6.0, 4.7.0
>         Environment: KVM, CentOS 7 mgmt + HV
>            Reporter: Nux
>              Labels: dashboard, kvm, sockets, statistics
>
> Hello,
> My current setup includes a dual cpu, quad core + HT, however in the ACS dashboard the
"CPU sockets" says only one.
> This value is wrong and as I undestand it, it is taken from "virsh nodeinfo" which is
known to give misleading information, as it reports stuff "per NUMA cell"
> As per the man page of virsh, the number of real physical sockets should be calculated
as "NUMA cell" multiplied by "CPU sockets".
> e.g.
> virsh nodeinfo
> CPU model:           x86_64
> CPU(s):              16
> CPU frequency:       2393 MHz
> CPU socket(s):       1
> Core(s) per socket:  4
> Thread(s) per core:  2
> NUMA cell(s):        2
> physical cpus = "CPU socket(s):       1"  *  "NUMA cell(s):        2" = 2 (correct)
> Additional information can be taken from "virsh capabilities|grep socket_id" (xml output)
e.g.:
> virsh capabilities|grep socket_id
>             <cpu id='0' socket_id='1' core_id='0' siblings='0,8'/>
>             <cpu id='2' socket_id='1' core_id='1' siblings='2,10'/>
>             <cpu id='4' socket_id='1' core_id='9' siblings='4,12'/>
>             <cpu id='6' socket_id='1' core_id='10' siblings='6,14'/>
>             <cpu id='8' socket_id='1' core_id='0' siblings='0,8'/>
>             <cpu id='10' socket_id='1' core_id='1' siblings='2,10'/>
>             <cpu id='12' socket_id='1' core_id='9' siblings='4,12'/>
>             <cpu id='14' socket_id='1' core_id='10' siblings='6,14'/>
>             <cpu id='1' socket_id='0' core_id='0' siblings='1,9'/>
>             <cpu id='3' socket_id='0' core_id='1' siblings='3,11'/>
>             <cpu id='5' socket_id='0' core_id='9' siblings='5,13'/>
>             <cpu id='7' socket_id='0' core_id='10' siblings='7,15'/>
>             <cpu id='9' socket_id='0' core_id='0' siblings='1,9'/>
>             <cpu id='11' socket_id='0' core_id='1' siblings='3,11'/>
>             <cpu id='13' socket_id='0' core_id='9' siblings='5,13'/>
>             <cpu id='15' socket_id='0' core_id='10' siblings='7,15'/>



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message