Re: [openstack-dev] [nova] Running large instances with CPU pinning and OOM

On 27.09.2017 14:46, Sahid Orentino Ferdjaoui wrote: > On Mon, Sep 25, 2017 at 05:36:44PM +0200, Jakub Jursa wrote: >> Hello everyone, >> >> We're experiencing issues with running large instances (~60GB RAM) on >> fairly large NUMA nodes (4 CPUs, 256GB R

Re: [openstack-dev] [nova] Running large instances with CPU pinning and OOM

On 27.09.2017 11:12, Jakub Jursa wrote: > > > On 27.09.2017 10:40, Blair Bethwaite wrote: >> On 27 September 2017 at 18:14, Stephen Finucane <sfinu...@redhat.com> wrote: >>> What you're probably looking for is the 'reserved_host_memory_mb' option. >>

Re: [openstack-dev] [nova] Running large instances with CPU pinning and OOM

On 27.09.2017 10:40, Blair Bethwaite wrote: > On 27 September 2017 at 18:14, Stephen Finucane wrote: >> What you're probably looking for is the 'reserved_host_memory_mb' option. >> This >> defaults to 512 (at least in the latest master) so if you up this to 4192 or >>

Re: [openstack-dev] [nova] Running large instances with CPU pinning and OOM

On 27.09.2017 10:14, Stephen Finucane wrote: > On Mon, 2017-09-25 at 17:36 +0200, Jakub Jursa wrote: >> Hello everyone, >> >> We're experiencing issues with running large instances (~60GB RAM) on >> fairly large NUMA nodes (4 CPUs, 256GB RAM) while using

[openstack-dev] [nova] Running large instances with CPU pinning and OOM

red on purpose when using cpu pinning? If yes, what is the reasoning behind it? And what would be the right solution to ensure having reserved RAM on the NUMA nodes? Thanks. Regards, Jakub Jursa __ OpenStack Development Mail