[openstack-dev] [octavia] Optimize the query of the octavia database

Adam Harwell flux.adam at gmail.com
Sat Sep 15 00:26:03 UTC 2018


It's high priority for me as well, so we should be able to get something
done very soon, I think. Look for something early next week maybe?

Thanks,
    --Adam

On Thu, Sep 13, 2018, 21:18 Jeff Yang <yjf1970231893 at gmail.com> wrote:

> Thanks:
>     I found the correlative patch in neutron-lbaas:
> https://review.openstack.org/#/c/568361/
>
>     The bug was marked high level by our QA team. I need to fix it as soon
> as possible.
>      Does Michael Johnson have any good suggestion? I am willing to
> complete the
>      repair work of this bug. If your patch still takes a while to prepare.
>
> Michael Johnson <johnsomor at gmail.com> 于2018年9月14日周五 上午7:56写道:
>
>> This is a known regression in the Octavia API performance. It has an
>> existing story[0] that is under development. You are correct, that
>> star join is the root of the problem.
>> Look for a patch soon.
>>
>> [0] https://storyboard.openstack.org/#!/story/2002933
>>
>> Michael
>> On Thu, Sep 13, 2018 at 10:32 AM Erik Olof Gunnar Andersson
>> <eandersson at blizzard.com> wrote:
>> >
>> > This was solved in neutron-lbaas recently, maybe we could adopt the
>> same method for Octavia?
>> >
>> > Sent from my iPhone
>> >
>> > On Sep 13, 2018, at 4:54 AM, Jeff Yang <yjf1970231893 at gmail.com> wrote:
>> >
>> > Hi, All
>> >
>> > As octavia resources increase, I found that running the "openstack
>> loadbalancer list" command takes longer and longer. Sometimes a 504 error
>> is reported.
>> >
>> > By reading the code, I found that octavia will performs complex left
>> outer join queries when acquiring resources such as loadbalancer, listener,
>> pool, etc. in order to only make one trip to the database.
>> > Reference code: http://paste.openstack.org/show/730022 Line 133
>> > Generated SQL statements: http://paste.openstack.org/show/730021
>> >
>> > So, I suggest that adjust the query strategy to provide different join
>> queries for different resources.
>> >
>> > https://storyboard.openstack.org/#!/story/2003751
>> >
>> >
>> __________________________________________________________________________
>> > OpenStack Development Mailing List (not for usage questions)
>> > Unsubscribe:
>> OpenStack-dev-request at lists.openstack.org?subject:unsubscribe
>> > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>> >
>> >
>> __________________________________________________________________________
>> > OpenStack Development Mailing List (not for usage questions)
>> > Unsubscribe:
>> OpenStack-dev-request at lists.openstack.org?subject:unsubscribe
>> > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>>
>> __________________________________________________________________________
>> OpenStack Development Mailing List (not for usage questions)
>> Unsubscribe:
>> OpenStack-dev-request at lists.openstack.org?subject:unsubscribe
>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>>
> __________________________________________________________________________
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: OpenStack-dev-request at lists.openstack.org?subject:unsubscribe
> 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/20180914/0d62f07e/attachment.html>


More information about the OpenStack-dev mailing list