Open Stack

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