cloudstack-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Jithin Raju <rajuj...@gmail.com>
Subject Re: Variable speed CPUs
Date Thu, 15 Aug 2013 17:35:27 GMT
Hi Pete,

Could you please compare your results with the output of dmidecode and 'cat
/proc/cpuinfo'

Thanks,
Jithin


On Thu, Aug 15, 2013 at 10:58 PM, Pete Johnson <pjohnson44@verizon.net>wrote:

> I'm using AMD FX-8320 8-core 3.5 GHz processors with 16GB of unbuffered
> ECC memory. (they're the best cost/performance processor available)
>
> - Pete
>
> -----Original Message----- From: Jithin Raju
> Sent: Thursday, August 15, 2013 1:04 PM
>
> To: users@cloudstack.apache.org
> Subject: Re: Variable speed CPUs
>
> Hi Marty,
>
> Not sure though, but I don't see the clock speed mentioned at the service
> offering is set as a configuration parameter of the guest OS for kvm.
>
> Rather the clock speed set for the service offering is used as a reference
> of the resource utilization while allocating host for the instances
> deployed using service offering.
>
> Pete: Which is the model number of the AMD processor you are using?
>
> From KVM perspective,We can specify the number of vCPUs to be allocated to
> guests, also it supports which physical CPU to use:
> "--cpuset=CPUSET
>         Set which physical cpus the guest can use. "CPUSET" is a comma
> separated list of numbers, which can also be specified in ranges or cpus to
> exclude. Example:
>
>             0,2,3,5     : Use processors 0,2,3 and 5
>             1-5,^3,8    : Use processors 1,2,4,5 and 8"
>
> Thanks,
> Jithin
>
>
> On Thu, Aug 15, 2013 at 10:08 PM, Marty Sweet <msweet.dev@gmail.com>
> wrote:
>
>  In KVM and cloudstack 4.1.1 VM clock speed is enforced by the service
>> offering set to the Guest VM.
>>
>> For example, if I were to make a service offering of 1vCPU running at 3Ghz
>> and I only have a host running (at clock speed) of 2Ghz then cloudstack
>> will refuse the start of the VM.
>>
>> You can see your processor statistics by running lshw -C CPU on the host,
>> the clock speed shown will be the actual host clock speed, regardless of
>> BIOS technologies which may throttle or boost the frequency at anytime
>> depending on load.
>>
>> Marty
>>
>> On Thursday, August 15, 2013, Pete Johnson wrote:
>>
>> > I am planning on running a mix of service offerings, mostly small but
>> > their will be some pretty large database/processing servers using 2+
>> cores.
>> >  Won't know how large yet.
>> >
>> > - Pete
>> >
>> > -----Original Message----- From: Bradley Hieber
>> > Sent: Thursday, August 15, 2013 12:07 PM
>> > To: users@cloudstack.apache.org
>> > Subject: Re: Variable speed CPUs
>> >
>> > What is the service offering for the guest machines? The service >
>> offering
>> > governs the type of virtual CPU presented to the guest.
>> >
>> >
>> > On Thu, Aug 15, 2013 at 12:04 PM, Pete Johnson <pjohnson44@verizon.net
>> > >wrote:
>> >
>> >  Hi,
>> >> I have build a small private cloud for an R&D project for one of my
>> >> clients.  I have 3 hosts each with 16gb memory and 8 cores (AMD) per
>> host.
>> >>    I’m using Cloudstack 4.1 and hosts are Ubuntu 12.04 w/KVM.   These
>> CPUs
>> >> can vary clock speeds based on bios settings which is enabled.  The
>> >> Cloudstack dashboard correctly estimates the CPU clock speed at its MAX
>> of
>> >> 3500 MHz.  But, when I log onto the guests and run virt-top it says
>> >> 1400MHz
>> >> which I assume is its current throttled down clock speed.  I am still
>> >> setting things up and have not had the chance to put the hosts under
>> >> enough
>> >> load to see of it clocks up.  My questions are:  Does Cloudstack >>
>> support
>> >> viewable clocked CPUs in hosts? How does Cloudstack support variable
>> >> clocked hosts from a real-time capacity load perspective and a usage
>> >> perspective.
>> >> Thanks
>> >> Pete Johnson
>> >>
>> >
>> >
>> >
>> >
>> > --
>> > Brad
>> >
>>
>>
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message