[openstack-dev] [tricircle] Port Query Performance Test

[Vega Cai]

Hi all,

I did a test about the performance of port query in Tricircle yesterday.
The result is attached.

Three observations in the test result:
(1) Neutron client costs much more time than curl, the reason may be
neutron client needs to apply for a new token in each run.
(2) Eventlet doesn't bring much improvement, the reason may be we only have
two bottom pods. I will add some logs to do a further investigation.
(3) Query 1000 ports in top pod costs about 1.5s when using curl, which is
acceptable.

BR
Zhiyuan


tricircle-query-test.xlsx
Description: MS-Excel 2007 spreadsheet
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [tricircle] Port Query Performance Test

[Kevin Benton]

+1. The neutron client can only operate on the environmental variables it
has access to, it doesn't store any other state. So if all it has is
credentials, it has to use those to fetch a token.

On Wed, Feb 3, 2016 at 12:05 PM, Rick Jones  wrote:

> On 02/03/2016 05:32 AM, Vega Cai wrote:
>
>> Hi all,
>>
>> I did a test about the performance of port query in Tricircle yesterday.
>> The result is attached.
>>
>> Three observations in the test result:
>> (1) Neutron client costs much more time than curl, the reason may be
>> neutron client needs to apply for a new token in each run.
>>
>
> Is "needs" a little strong there?  When I have been doing things with
> Neutron CLI at least and needed to issue a lot of requests over a somewhat
> high latency path, I've used the likes of:
>
> token=$(keystone token-get | awk '$2 == "id" {print$4}')
> NEUTRON="neutron --os-token=$token --os-url=https://mutter
>
> to avoid grabbing a token each time.  Might that be possible with what you
> are testing?
>
> rick jones
>
> __
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>



-- 
Kevin Benton
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [tricircle] Port Query Performance Test

[Rick Jones]

On 02/03/2016 05:32 AM, Vega Cai wrote:

Hi all,

I did a test about the performance of port query in Tricircle yesterday.
The result is attached.

Three observations in the test result:
(1) Neutron client costs much more time than curl, the reason may be
neutron client needs to apply for a new token in each run.


Is "needs" a little strong there?  When I have been doing things with 
Neutron CLI at least and needed to issue a lot of requests over a 
somewhat high latency path, I've used the likes of:


token=$(keystone token-get | awk '$2 == "id" {print$4}')
NEUTRON="neutron --os-token=$token --os-url=https://mutter

to avoid grabbing a token each time.  Might that be possible with what 
you are testing?


rick jones

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev