We tried this a while back, but it wasn't entirely clear whether we were introducing new bottlenecks. That said, the 2 approaches we experimented with were:
* pre-generating a list of signed URLs and running them through httperf * using oauth-proxy (http://github.com/mojodna/oauth-proxy) with apachebench (httperf doesn't have proxy support) to sign URLs on the fly. oauth-proxy is a Twisted server, so it shouldn't have affected concurrency numbers, but we didn't keep track of the overhead that the signing introduced. I was thinking that it might be useful to hack OAuth support into JMeter in order to be able to use that, but never got that far. I hope this helps. seth On Sun, Mar 22, 2009 at 4:49 PM, Perryn Fowler <[email protected]> wrote: > > Has anyone performed load testing on an oAuth provider? If so, what did you > use? > > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "OAuth" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/oauth?hl=en -~----------~----~----~----~------~----~------~--~---
