# Benchmarking

**URL:** <https://www.ruby-forum.com/t/benchmarking/116316>\
**Category:** Deployment\
**Created:** [October 4, 2007, 1:47pm UTC](https://www.ruby-forum.com/t/benchmarking/116316 "2007-10-04T13:47:43Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![softf5ajivanet](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/s/9f8e36/32.png) [@softf5ajivanet](https://www.ruby-forum.com/u/softf5ajivanet)\
**Post date:** [October 4, 2007, 1:47pm UTC](https://www.ruby-forum.com/t/benchmarking/116316/1 "2007-10-04T13:47:43Z")

</div>

I’ve got an app I’m building for some friends running on a SliceHost box  
written in Ruby on Rails.

I’m looking to benchmark it to see how many requests it could feasibly  
take and what kind of spec / requirements we’re gonna need for scaling  
it up.

Looking for any pointers in this area as benchmarking is a bit of a gray  
area for me.

Appreciate it,

John.

---

<div class="post-metadata">

**Author:** ![softf5ajivanet](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/s/9f8e36/32.png) [@softf5ajivanet](https://www.ruby-forum.com/u/softf5ajivanet)\
**Post date:** [October 4, 2007, 9:37pm UTC](https://www.ruby-forum.com/t/benchmarking/116316/2 "2007-10-04T21:37:36Z")

</div>

John G. wrote:

> Appreciate it,
> 
> John.

There’s a Peepcode screencast ($9) that might help –  
[http://peepcode.com/products/benchmarking-with-httperf](http://peepcode.com/products/benchmarking-with-httperf)

## –

Autopendium :: Stuff about old cars  
[http://autopendium.com](http://autopendium.com)

---

<div class="post-metadata">

**Author:** ![softf5ajivanet](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/s/9f8e36/32.png) [@softf5ajivanet](https://www.ruby-forum.com/u/softf5ajivanet)\
**Post date:** [October 5, 2007, 4:31am UTC](https://www.ruby-forum.com/t/benchmarking/116316/3 "2007-10-05T04:31:05Z")

</div>

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](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.

[1] [ab - Apache HTTP server benchmarking tool - Apache HTTP Server](http://httpd.apache.org/docs/2.0/programs/ab.html)

–  
Maykel Rodriguez

> **[Home - Speedyrails](https://www.speedyrails.com/)**
>
> Speedyrails is an AWS Advanced Consulting Partner. We leverage our extensive AWS knowledge to provide exceptional managed services.

Easy to use Rails hosting

---

<div class="post-metadata">

**Author:** ![softf5ajivanet](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/s/9f8e36/32.png) [@softf5ajivanet](https://www.ruby-forum.com/u/softf5ajivanet)\
**Post date:** [October 8, 2007, 12:57pm UTC](https://www.ruby-forum.com/t/benchmarking/116316/4 "2007-10-08T12:57:09Z")

</div>

removed\_email\_address@domain.invalid 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](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 K. [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](http://railsexpress.de)

–  
Roderick van Domburg  
[http://www.nedforce.com](http://www.nedforce.com)