Open Stack

Hi Folks,

I just want to give you an update on this topic, we opened a bug against this behavior:
https://bugs.launchpad.net/quantum/+bug/1075369

Bug Description:
In quantum when a new network is created and system checks for user's quota, instead of getting a count from DB object, it returns all objects from db and locally counts them all. It has performance implications when the number of objects increases.

We will submit the patch ASAP.

Thanks,

Edgar

From: Salvatore Orlando <sorlando at nicira.com<mailto:sorlando at nicira.com>>
Reply-To: OpenStack List <openstack-dev at lists.openstack.org<mailto:openstack-dev at lists.openstack.org>>
Date: Wednesday, October 31, 2012 12:54 AM
To: "gkotton at redhat.com<mailto:gkotton at redhat.com>" <gkotton at redhat.com<mailto:gkotton at redhat.com>>, OpenStack List <openstack-dev at lists.openstack.org<mailto:openstack-dev at lists.openstack.org>>
Subject: Re: [openstack-dev] Quantum Performance

Edgar,

My suspicion here goes to the IP allocation mechanisms.
Hence, I'd try to run the following tests (they should be easily scriptable):

1) Create networks no subnets
2) Create networks, with subnet having a small CIDR (say /28)
3) Create networks with larger CIDRs (say /24, /20, /16 etc)

What behaviour do you observe in the above three cases?

Also, It might be worth shutting down agent to pinpoint whether the problem is in Quantum service itself on in the interactions with the various agents.

Salvatore

PS: thanks for doing these tests - They've been lying on my TODO list for way too much time!
If you don't hate me too much for the service insertion story, I'll be glad to buy you a drink at the next summit :)


On 31 October 2012 08:37, Gary Kotton <gkotton at redhat.com<mailto:gkotton at redhat.com>> wrote:
On 10/31/2012 09:48 AM, Edgar Magana (eperdomo) wrote:
Hi Folks,

I am running OpenStack Folsom with Quantum/OVS plugin. I am running some performance tests for Quantum, basically I am creating 5000 network with one subnet each one of them.
After the first ~50 – 70 networks the system response time is slower and slower, to the point that it could take up to ~6 - 7 seconds to create just a network and the same for the subnets.

Hi,
Is the problem you are seeing with the Quantum service or the agents? Off the bat I would say that it is with the Quantum service. Are the calls done in parallel or are they done sequentially?

There are a number of things that we should do to isolate this:
1. Check the internal logic of the network creation. Basically there are 3 stages:
     i. provider network treatment
    ii network create
    iii. l3 notification
It would be interesting to see who eats the most time.
2. Need to profile database access

Thanks
Gary

I would like to know if somebody else has experimented this kind of behavior in Quantum or even in nova-network.

Thanks,

Edgar




_______________________________________________
OpenStack-dev mailing list
OpenStack-dev at lists.openstack.org<mailto:OpenStack-dev at lists.openstack.org>http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev


_______________________________________________
OpenStack-dev mailing list
OpenStack-dev at lists.openstack.org<mailto:OpenStack-dev at lists.openstack.org>
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20121106/6f754375/attachment.html>