The bug is hanging in Incomplete for more than a month for MOS project.
Hence moving to invalid.
** Changed in: mos/6.0.x
Status: Incomplete => Invalid
** Changed in: mos/6.1.x
Status: Incomplete => Invalid
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to Keystone.
https://bugs.launchpad.net/bugs/1157261
Title:
Performance issue on high concurrency
Status in OpenStack Identity (Keystone):
Triaged
Status in Mirantis OpenStack:
Invalid
Status in Mirantis OpenStack 6.0.x series:
Invalid
Status in Mirantis OpenStack 6.1.x series:
Invalid
Bug description:
Im currently using Keystone as the auth-server in Swift.
We have done performance test on our solution and we found that performance
of keystone+swift is quite low, only 200 ops/s. While with the same setup the
throughput can be improved to 7k ops/s by replacing keystone with swauth
We found the keystone process is fully saturating one sandy bridge core. This
looks like a scalability issue.
Would be good if keystone could scale up well on a multi-core server.
To manage notifications about this bug go to:
https://bugs.launchpad.net/keystone/+bug/1157261/+subscriptions
--
Mailing list: https://launchpad.net/~yahoo-eng-team
Post to : yahoo-eng-team@lists.launchpad.net
Unsubscribe : https://launchpad.net/~yahoo-eng-team
More help : https://help.launchpad.net/ListHelp
