yahoo-eng-team team mailing list archive

[Dmitry Mescheryakov <1157261@xxxxxxxxxxxxxxxxxx>]

** Also affects: mos/6.0.x
   Importance: Critical
     Assignee: Aleksandr Shaposhnikov (alashai8)
       Status: Incomplete

** Also affects: mos/6.1.x
   Importance: Undecided
       Status: New

** Changed in: mos/6.1.x
   Importance: Undecided => Critical

** Changed in: mos/6.1.x
       Status: New => Incomplete

** Changed in: mos/6.1.x
     Assignee: (unassigned) => Aleksandr Shaposhnikov (alashai8)

** Changed in: mos/6.1.x
    Milestone: None => 6.1

** Changed in: mos/6.0.x
    Milestone: 6.0 => 6.0.1

-- 
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:
  Incomplete
Status in Mirantis OpenStack 6.0.x series:
  Incomplete
Status in Mirantis OpenStack 6.1.x series:
  Incomplete

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