- Original Message -
> From: "Arne Wiebalck"
> To: "Steve Gordon"
> Cc: "Manuel Sopena Ballesteros" ,
> openstack@lists.openstack.org
> Sent: Tuesday, February 7, 2017 2:00:23 PM
> Subject: Re: [Openstack] nova assign isntances to cpu p
;> <mailto:arne.wieba...@cern.ch>>
>>>> To: "Manuel Sopena Ballesteros" >>> <mailto:manuel...@garvan.org.au>>
>>>> Cc: openstack@lists.openstack.org <mailto:openstack@lists.openstack.org>
>>>> Sent: Tuesday, February 7,
ists.openstack.org <mailto:openstack@lists.openstack.org>
>> Sent: Tuesday, February 7, 2017 2:46:39 AM
>> Subject: Re: [Openstack] nova assign isntances to cpu pinning
>>
>> Manuel,
>>
>> Rather than with aggregate metadata we assign instances to NUMA nodes
- Original Message -
> From: "Arne Wiebalck"
> To: "Manuel Sopena Ballesteros"
> Cc: openstack@lists.openstack.org
> Sent: Tuesday, February 7, 2017 2:46:39 AM
> Subject: Re: [Openstack] nova assign isntances to cpu pinning
>
> Manuel,
>
>
On 02/06/2017 06:19 PM, Manuel Sopena Ballesteros wrote:
Hi,
I am trying to isolate my instances by cpu socket in order to improve my NUMA
hardware performance.
What would be the recommended way to do this?
In order to dedicate a host CPU to each virtual CPU, set the flavor extra spec
"h
Hi Sinh,
Depending on flavor size and benchmark, we were able to reduce the loss compared
to bare metal from 8-20% to 3-5%. Details can be found on our blog:
http://openstack-in-production.blogspot.ch/2015/08/numa-and-cpu-pinning-in-high-throughput.html
and in more depth in this presentation:
h
hi arne,
do you happen to have performance numbers before and after creating guests
with and without the cpu pinning options?
thanks.
Sinh
On Mon, Feb 6, 2017 at 11:46 PM, Arne Wiebalck
wrote:
> Manuel,
>
> Rather than with aggregate metadata we assign instances to NUMA nodes via
> flavor ex
Manuel,
Rather than with aggregate metadata we assign instances to NUMA nodes via
flavor extra_specs,
i.e. nova flavor-show reports something like
—>
| extra_specs| {"hw:numa_nodes": "1"} |
<—
for our NUMA-aware flavors.
This seems to work pretty well and gives the desired p
: [Openstack] nova assign isntances to cpu pinning
Hi,
I am trying to isolate my instances by cpu socket in order to improve my NUMA
hardware performance.
[root@openstack-dev ~(keystone_admin)]# nova aggregate-set-metadata numa
pinned=true
Metadata has been successfully updated for aggregate 1
Hi,
I am trying to isolate my instances by cpu socket in order to improve my NUMA
hardware performance.
[root@openstack-dev ~(keystone_admin)]# nova aggregate-set-metadata numa
pinned=true
Metadata has been successfully updated for aggregate 1.
+++++-
10 matches
Mail list logo