incubator-cloudstack-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Tamas Monos <tam...@veber.co.uk>
Subject RE: Vmware CPU Cap
Date Tue, 22 May 2012 22:43:29 GMT
Hi,

No I don't think this is a bug. When you set 1000Mhz as CPU cap that is meant per core. vmWare
will limit each CPU core to 1000Mhz.
As you gave 2 CPU cores that is 2000Mhz effective. That is how vmware works.

I have setup my offerings all to 1000Mhz as speed and just increasing the number of cores.
1 core ends up being 1x1000Mhz
2 core ends up being 2x1000Mhz=2000Mhz 
...
...

I'm actually using it in production and works quite well as Cloudstack "allocates" 4000Mhz
when I'm using 4x1000Mhz cores and vmware cleverly balances between the cores as you put load
on it and not letting any of the cores above the set limit of 1000Mhz.

Regards

-----Original Message-----
From: Diego Spinola Castro [mailto:spinolacastro@gmail.com] 
Sent: 22 May 2012 19:34
To: cloudstack-dev@incubator.apache.org
Subject: Re: Vmware CPU Cap

I forgot the link:
http://imageshack.us/photo/my-images/848/cpulimit.png/

2012/5/22 Diego Spinola Castro <spinolacastro@gmail.com>

> I believe that is a bug with cpu cap and vmware.
>
> To reproduce:
>
> Create a offering with 2 cores and 1000mhz.
> Enable CPU CAP.
>
> After created instance , cs create a vm with 2 cores and 1000mhz of limit.
>
> I don't know for sure if is a bug, but vmware gives 1000mhz shared 
> with cores.
>
>
>
> Diego
>


Mime
View raw message