Hi James, True that static NUMA placement would work (well, it would if this was fixed: https://bugs.launchpad.net/nova/+bug/1517006). But the issue with the static approach is that it requires flavor definitions and imposes stricter scheduling constraints in order to meet the pre-defined flavor NUMA topology and policy.
We're doing science computing and hpc on OpenStack (using libvirt/kvm on ubuntu as hypervisor) and have done a bit of performance testing with strict NUMA policy versus numad. We've done some benchmarking of whole- node VM instances (as would be the case with most hpc workloads) and found that for the most part numad does a near enough job to static pinning (i.e., setting the guest up to mirror the host) that we would prefer to just use numad and get more performance without compromising scheduling flexibility. We'd also do this in our general purpose zones/cells where we have all sorts of mixed research workloads. Hope that helps explain it? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1574883 Title: libvirt not configured with numad support To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1574883/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
