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

2016-02-03 Thread 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

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

2016-02-03 Thread 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,

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

2016-02-03 Thread 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