[openstack-dev] [Neutron] One performance issue about VXLAN pool initiation

Xurong Yang idopra at gmail.com
Fri May 30 02:58:09 UTC 2014


Hi,
Thanks for your response, yes, i get the reason, so, That's why i question
that whether one good solution can have a high performance with a large
vxlan range? if possible, a blueprint is deserved to consider.

Tanks,
Xurong Yang


2014-05-29 18:12 GMT+08:00 ZZelle <zzelle at gmail.com>:

> Hi,
>
>
> vxlan network are inserted/verified in DB one by one, which could explain
> the time required
>
>
> https://github.com/openstack/neutron/blob/master/neutron/plugins/ml2/drivers/type_vxlan.py#L138-L172
>
> Cédric
>
>
>
> On Thu, May 29, 2014 at 12:01 PM, Xurong Yang <idopra at gmail.com> wrote:
>
>> Hi, Folks,
>>
>> When we configure VXLAN range [1,16M], neutron-server service costs long
>> time and cpu rate is very high(100%) when initiation. One test base on
>> postgresql has been verified: more than 1h when VXLAN range is [1, 1M].
>>
>> So, any good solution about this performance issue?
>>
>> Thanks,
>> Xurong Yang
>>
>>
>>
>> _______________________________________________
>> OpenStack-dev mailing list
>> 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
> 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/20140530/36e7df47/attachment.html>


More information about the OpenStack-dev mailing list