[EMAIL PROTECTED] wrote: > I would also recommend httperf but you can do some basic benchmarks > using the ab (ApacheBenchmark [1]) command, something like: > > ab -n 1000 -c 100 http://www.mysite.com/mycontroller/myaction > > will do 1000 requests to the given URL with a concurrency of 100, the > result is a detailed report.
Finally there's railsbench by Stefan Kaes [1] that gives you more insight into the inner workings of your Rails application. Also note that httperf comes greatly recommended over ab for performance testing. It's way more accurate and not particularly tougher to get a grip of than ab. [1] http://railsexpress.de -- Roderick van Domburg http://www.nedforce.com -- Posted via http://www.ruby-forum.com/. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Deploying Rails" group. To post to this group, send email to rubyonrails-deployment@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/rubyonrails-deployment?hl=en -~----------~----~----~----~------~----~------~--~---
