Open Stack

If there was going to be a benchmark suite for keystone, I'd suggest
contributing it to keystoneclient rather than keystone itself. That said,
here's an example of a one liner exercising v3 auth:

$ keystone --os-token=ADMIN
--os-endpoint=http://localhost:35357/v2.0/bootstrap --user-name=admin
--pass=admin --tenant-name=admin
--role-name=admin
$ cat auth-v3.json
{"auth": {"identity": {"methods": ["password"], "password": {"user":
{"name": "admin", "password": "admin", "domain": {"id": "default"}}}},
"scope": {"project": {"name": "admin", "domain": {"id": "default"}}}}}
This is ApacheBench, Version 2.3 <$Revision: 1373084 $>
Copyright 1996 Adam Twiss, Zeus Technology Ltd, http://www.zeustech.net/
Licensed to The Apache Software Foundation, http://www.apache.org/

Benchmarking 127.0.0.1 (be patient).....done


Server Software:
Server Hostname:        127.0.0.1
Server Port:            35357

Document Path:          /v3/auth/tokens
Document Length:        463 bytes

Concurrency Level:      16
Time taken for tests:   16.192 seconds
Complete requests:      100
Failed requests:        0
Write errors:           0
Total transferred:      66700 bytes
Total body sent:        36200
HTML transferred:       46300 bytes
Requests per second:    6.18 [#/sec] (mean)
Time per request:       2590.670 [ms] (mean)
Time per request:       161.917 [ms] (mean, across all concurrent requests)
Transfer rate:          4.02 [Kbytes/sec] received
                        2.18 kb/s sent
                        6.21 kb/s total

Connection Times (ms)
              min  mean[+/-sd] median   max
Connect:        0    0   0.2      0       1
Processing:   222 2399 524.8   2581    2641
Waiting:      222 2399 524.8   2581    2641
Total:        223 2399 524.6   2581    2641

Percentage of the requests served within a certain time (ms)
  50%   2581
  66%   2596
  75%   2610
  80%   2616
  90%   2626
  95%   2634
  98%   2639
  99%   2641
 100%   2641 (longest request)

This is just on my i5 laptop w/ sqlite db on disk, so while keystone is
slow, this is even slower.



-Dolph


On Fri, Mar 22, 2013 at 11:47 AM, Chmouel Boudjnah <chmouel at chmouel.com>wrote:

> Adding Joe email to the discussion since he's not subscribed on
> openstack-dev@
>
> On Fri, Mar 22, 2013 at 5:40 PM, heckj <heckj at mac.com> wrote:
> > We don't have any explicit benchmarking scripts set up and captured for
> Keystone in keystone's code base.
> >
> > I've been doing benchmarking and live-system analysis, in my case based
> on post-processing of proxy log output and then reporting latency and
> processing times for various API calls. My analysis has been mostly whole
> system and a specific configuration. The logs were generated using various
> "work the cloud" continual load tests.
> >
> > For single-point direct analysis, you could use any testing system you
> like that generates HTTP request with specific bodies and headers -
> grinder, locust, etc. I don't know if anyone working on Tempest has done
> similar things or not.
> >
> > - joe
> >
> > On Mar 22, 2013, at 7:47 AM, Joe Hakim Rahme <
> joe.hakim.rahme at enovance.com> wrote:
> >> I wrote a short benchmark script that launches multiple requests to
> >> Keystone and measures the response time to get the authentication
> >> token. Since I couldn't find anything that does this in Keystone, I
> >> thought it'd be a good idea to add a benchmark tool. Swift already has
> >> something similar (common/bench.py).
> >>
> >> Since I am new to the community (and OpenStack in general) I thought I'd
> >> consult with you here to avoid going in a wrong direction. So here are a
> >> few questions:
> >>
> >> - Is there an existing script that does this and that I might have
> >>   missed?
> >> - What features would you suggest I include in this tool?
> >> - Should I follow (reuse?) what's already done for the Swift bench?
> >>
> >> Thank you for your answers,
> >> J.
> >>
> >> _______________________________________________
> >> OpenStack-dev mailing list
> >> OpenStack-dev at lists.openstack.org
> >> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
> >
> >
> > _______________________________________________
> > OpenStack-dev mailing list
> > OpenStack-dev at lists.openstack.org
> > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
> _______________________________________________
> OpenStack-dev mailing list
> OpenStack-dev at lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20130322/b048ba89/attachment.html>