Reza,
There was a good presentation on different token formats during Tokyo
summit. It may help answering some of the questions.
https://www.openstack.org/summit/tokyo-2015/videos/presentation/deep-dive-into-keystone-tokens-and-lessons-learned
On Sat, Nov 7, 2015 at 10:24 AM, Reza Bakhshayeshi
Thanks all for your tips,
I switched to Fernet token and average response time reduced to 6.8 seconds.
I think, as Clint said, I have to balance the load between multiple tinier
keystone servers.
What's your opinion?
Dina,
No, I just used Apache JMeter.
Regards,
Reza
On 27 October 2015 at 04:33,
Reza,
afair the number of tokens that can be processed simultaneously by Keystone
in reality is equal to the number of Keystone workers (either admin workers
or public workers, depending on the user's nature). And this number
defaults to the number of CPUs. So that is kind of default limitation, t
Excerpts from Reza Bakhshayeshi's message of 2015-10-27 05:11:28 +0900:
> Hi all,
>
> I've installed OpenStack Kilo (with help of official document) on a
> physical HP server with following specs:
>
> 2 Intel(R) Xeon(R) CPU E5-2695 v2 @ 2.40GHz each 12 physical core (totally
> 48 threads)
> and 1
Hi all,
I've installed OpenStack Kilo (with help of official document) on a
physical HP server with following specs:
2 Intel(R) Xeon(R) CPU E5-2695 v2 @ 2.40GHz each 12 physical core (totally
48 threads)
and 128 GB of Ram
I'm going to benchmark keystone performance (with Apache JMeter) in order
