Re: [libvirt] Ongoing work on lock contention in qemu driver?

2013-06-03 Thread Daniel P. Berrange
On Fri, May 24, 2013 at 11:37:04AM -0400, Peter Feiner wrote: On Wed, May 22, 2013 at 7:31 PM, Peter Feiner pe...@gridcentric.ca wrote: Since some security driver operations are costly, I think it's worthwhile to reduce the scope of the security manager lock or increase the granularity by

Re: [libvirt] Ongoing work on lock contention in qemu driver?

2013-05-24 Thread Peter Feiner
On Wed, May 22, 2013 at 7:31 PM, Peter Feiner pe...@gridcentric.ca wrote: Since some security driver operations are costly, I think it's worthwhile to reduce the scope of the security manager lock or increase the granularity by introducing more locks. After a cursory look, the security manager

Re: [libvirt] Ongoing work on lock contention in qemu driver?

2013-05-22 Thread Peter Feiner
One theory I had was that the virDomainObjListSearchName method could be a bottleneck, becaue that acquires a lock on every single VM. This is invoked when starting a VM, when we call virDomainObjListAddLocked. I tried removing this locking though didn't see any performance

[libvirt] Ongoing work on lock contention in qemu driver?

2013-05-16 Thread Peter Feiner
Hello Daniel, I've been working on improving scalability in OpenStack on libvirt+kvm for the last couple of months. I'm particularly interested in reducing the time it takes to create VMs when many VMs are requested in parallel. One apparent bottleneck during virtual machine creation is libvirt.

Re: [libvirt] Ongoing work on lock contention in qemu driver?

2013-05-16 Thread Daniel P. Berrange
On Thu, May 16, 2013 at 12:09:39PM -0400, Peter Feiner wrote: Hello Daniel, I've been working on improving scalability in OpenStack on libvirt+kvm for the last couple of months. I'm particularly interested in reducing the time it takes to create VMs when many VMs are requested in parallel.

Re: [libvirt] Ongoing work on lock contention in qemu driver?

2013-05-16 Thread Peter Feiner
How many CPU cores are you testing on ? That's a good improvement, but I'd expect the improvement to be greater as # of core is larger. I'm testing on 12 Cores x 2 HT per code. As I'm working on teasing out software bottlenecks, I'm intentionally running fewer tasks (20 parallel creations)

Re: [libvirt] Ongoing work on lock contention in qemu driver?

2013-05-16 Thread Daniel P. Berrange
On Thu, May 16, 2013 at 01:00:15PM -0400, Peter Feiner wrote: How many CPU cores are you testing on ? That's a good improvement, but I'd expect the improvement to be greater as # of core is larger. I'm testing on 12 Cores x 2 HT per code. As I'm working on teasing out software

Re: [libvirt] Ongoing work on lock contention in qemu driver?

2013-05-16 Thread Peter Feiner
On Thu, May 16, 2013 at 1:18 PM, Daniel P. Berrange berra...@redhat.com wrote: On Thu, May 16, 2013 at 01:00:15PM -0400, Peter Feiner wrote: How many CPU cores are you testing on ? That's a good improvement, but I'd expect the improvement to be greater as # of core is larger. I'm testing

Re: [libvirt] Ongoing work on lock contention in qemu driver?

2013-05-16 Thread Daniel P. Berrange
On Thu, May 16, 2013 at 06:18:57PM +0100, Daniel P. Berrange wrote: On Thu, May 16, 2013 at 01:00:15PM -0400, Peter Feiner wrote: How many CPU cores are you testing on ? That's a good improvement, but I'd expect the improvement to be greater as # of core is larger. I'm testing on 12