Comment 1 for bug 1643006

I've ran some tests against keystone while the overcloud deploy is ongoing, at some stages keystone is taking 2 minutes to authenticate a token.

The DB isn't being overly stressed, I'm thinking the keystone-admin python process is CPU bound and we only have one of them, it doesn't scale with the CPU's.

I've also tried tweaking the WSGI config (specifically the number of processes) and tested it with the "ab" bench marking tool, nothing I could do increase the number of requests keystone-admin cloud process(about 3 per second).