>
> Have you taken into consideration the TCP setup connection into your
> profiling?
>
> TCP’s slow start process, window size learning etc?
>
> I feel this could have considerable impact unless you have run few
> thousand cycles to average out the time taken so that t
Hi Vladimir,
I can try and help with some of the keystone troubleshooting, but we might
need some more information.
On Fri, May 5, 2017 at 9:00 AM, Vladimir Prokofev wrote:
> Writing things down always helps.
> So I dug a little further, and seems that keystone is the weakest link.
> It appears
On 5/5/2017 9:00 AM, Vladimir Prokofev wrote:
Writing things down always helps.
So I dug a little further, and seems that keystone is the weakest link.
It appears that it takes 500-600ms to generate a token, similar time to
validate it. This means that first time application accesses the API
requ
Writing things down always helps.
So I dug a little further, and seems that keystone is the weakest link.
It appears that it takes 500-600ms to generate a token, similar time to
validate it. This means that first time application accesses the API
request will run at least 1000ms, or even more. Seco
Hello Ops.
So I had a feeling that my Openstack API is running a bit slow, like it
takes a couple of seconds to get a full list of all instances in Horizon
for example, which is kind of a lot for a basic MySQL select-and-present
job. This got me wondering to how can I measure execution times and f
