On 07/15/2015 04:57 PM, Dugger, Donald D wrote:
In re: Static CPU frequency. For modern Intel CPUs this really isn't true.
Turbo Boost is a feature that allows certain CPUs in certain conditions to
actually run at a higher clock rate that what is advertised at power on (the
havoc this causes
-Original Message-
From: Chris Friesen [mailto:chris.frie...@windriver.com]
Sent: Thursday, July 16, 2015 12:07 AM
To: openstack-dev@lists.openstack.org
Subject: Re: [openstack-dev] [nova] schedule instance based on CPU frequency ?
On 07/15/2015 04:57 PM, Dugger, Donald D wrote:
In re: Static CPU
. Gale
Ph: 303/443-3786
-Original Message-
From: Jay Pipes [mailto:jaypi...@gmail.com]
Sent: Friday, July 3, 2015 7:26 AM
To: openstack-dev@lists.openstack.org
Subject: Re: [openstack-dev] [nova] schedule instance based on CPU frequency ?
On 07/03/2015 06:32 AM, Sylvain Bauza wrote:
Le 02/07
I propose a review to add it in cpu_info :
https://review.openstack.org/#/c/197829/
2015-07-03 21:37 GMT+08:00 Sylvain Bauza sba...@redhat.com:
Le 03/07/2015 15:25, Jay Pipes a écrit :
On 07/03/2015 06:32 AM, Sylvain Bauza wrote:
Le 02/07/2015 21:40, Jay Pipes a écrit :
On 07/01/2015
On 07/03/2015 06:32 AM, Sylvain Bauza wrote:
Le 02/07/2015 21:40, Jay Pipes a écrit :
On 07/01/2015 12:23 AM, ChangBo Guo wrote:
thanks Dan and Jay, we don't need add new scheduler for that :-),
what about provide cpu frequency to api /os-hypervisors, that means
we can
report this value
Le 02/07/2015 21:40, Jay Pipes a écrit :
On 07/01/2015 12:23 AM, ChangBo Guo wrote:
thanks Dan and Jay, we don't need add new scheduler for that :-),
what about provide cpu frequency to api /os-hypervisors, that means
we can
report this value automatically, the value can be used in high
On 07/01/2015 12:23 AM, ChangBo Guo wrote:
thanks Dan and Jay, we don't need add new scheduler for that :-),
what about provide cpu frequency to api /os-hypervisors, that means
we can
report this value automatically, the value can be used in high level
mange tools.
Meh, I'm not too big
On 06/30/2015 07:42 AM, ChangBo Guo wrote:
CPU frequency is an import performance parameter, currently nova
drivers just report cpu_info without frequency. we stored the compute
node cpu_info in database with colum compute_nodes.cpu_info, we can add
the frequency easily.
The usage
On Tue, Jun 30, 2015 at 02:42:01PM +0800, ChangBo Guo wrote:
CPU frequency is an import performance parameter, currently nova drivers
just report cpu_info without frequency. we stored the compute node
cpu_info in database with colum compute_nodes.cpu_info, we can add the
frequency
thanks Dan and Jay, we don't need add new scheduler for that :-),
what about provide cpu frequency to api /os-hypervisors, that means we
can
report this value automatically, the value can be used in high level mange
tools.
2015-07-01 2:58 GMT+08:00 Jay Pipes jaypi...@gmail.com:
On
2015-06-30 16:38 GMT+08:00 Nikola Đipanov ndipa...@redhat.com:
On 06/30/2015 07:42 AM, ChangBo Guo wrote:
CPU frequency is an import performance parameter, currently nova
drivers just report cpu_info without frequency. we stored the compute
node cpu_info in database with colum
On 06/30/2015 02:42 AM, ChangBo Guo wrote:
CPU frequency is an import performance parameter, currently nova
drivers just report cpu_info without frequency. we stored the compute
node cpu_info in database with colum compute_nodes.cpu_info, we can add
the frequency easily.
The usage of
CPU frequency is an import performance parameter, currently nova drivers
just report cpu_info without frequency. we stored the compute node
cpu_info in database with colum compute_nodes.cpu_info, we can add the
frequency easily.
The usage of cpu frequency I can think is used to
13 matches
Mail list logo
