yahoo-eng-team team mailing list archive

Thread
Date

[Bug 1157261] Re: performance issue on high concurrency

To: yahoo-eng-team@xxxxxxxxxxxxxxxxxxx
From: Aleksandr Shaposhnikov <alashai8@xxxxxxxxx>
Date: Wed, 19 Nov 2014 22:58:26 -0000
Reply-to: Bug 1157261 <1157261@xxxxxxxxxxxxxxxxxx>
Sender: bounces@xxxxxxxxxxxxx

** Also affects: mos
   Importance: Undecided
       Status: New

** Changed in: mos
   Importance: Undecided => Critical

** Changed in: mos
    Milestone: None => 6.0

-- 
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:
  New

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