New to Rails 3? Check out the Ruby on Rails 3 Tutorial book and screencast.

A book and screencast series showing you how to develop and deploy industrial-strength Rails apps in a direct, step by step way. The screencast series includes 12 lessons over more than 15 hours! Get the best "over the shoulder" experience of following what a top Rails 3 developer does when building an app today. Click here to learn more.

State of the Stack: Who's Using What In Production

In Deployment, News

railslabstate.pngRecently, as part of their new RailsLab site, New Relic released The State of the Stack: A Ruby on Rails Benchmarking Report.

Despite the title, I don't think it's a benchmarking report at all, but it does present some useful information collected from the production environments of over 1000 New Relic customers. You can see which versions of Ruby and Rails are the most popular in production amongst New Relic customers, as well as the Rails plugins that are used the most. It's important to remember, of course, that New Relic customers are not necessarily representative of the entire Ruby and Rails community.

Ruby 1.8.6 running on a 64 bit Linux takes 36.1% of the Ruby interpreter market here, with 1.8.6 on a 32 bit Linux taking second place and 1.8.6 on OS X coming in third. 1.8.7 sees very little action, and JRuby's first appearance is with just 0.7% of the market. On the Rails front, there's a similar distribution, with Rails 2.2.2 taking 37%, 2.1.0 with 15.5%, and 2.1.2 with 9.6%. Rails 1.x is still in use by a few percent of users.

The top five most popular plugins are exception_notification, restful_authentication, will_paginate, attachment_fu, and acts_as_list.

Disclaimer: New Relic is a sponsor of Rails Inside. This is not a sponsored post, however.

Post to Twitter Tweet This Post

Vaguely Related Posts (Usually)

4 Comment Responses to “State of the Stack: Who's Using What In Production”

  1. #1
    Mike Malloy Says:

    Peter. Thanks for the note about the State of the Stack. We describe it as a benchmarking report believing that many dev teams don't have a good idea how their own deployment may compare to other apps or other companies. So this gives them some insights into how other teams construct the app stack and how they customize it with various plugins. It may not be a benchmark in the strict ITIL, Deming, Baldrige sense, but it provides a point of comparison for developers everywhere.
    Mike at New Relic

  2. #2
    Peter Cooper Says:

    Oh I get you now. For some reason the other meaning of benchmark didn't cross my mind!

  3. #3
    Chris Kottom Says:

    Over 1500 users and not enough of those using Ruby 1.9 in production yet to show up on the chart? Really?

  4. #4
    Peter Cooper Says:

    I'd believe it. I don't personally know of anyone using 1.9 in production yet. I think it's still a little too early (unless, of course, your testing is so rock solid that you're confident your app will run fine - then it's worth trying).

Leave a Reply