Databases
StackOverflow2013
Postsdbo
POIs Ruby 1.9.1 actually ready and faster for a new Rails deployment?
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POIs Ruby 1.9.1 actually ready and faster for a new Rails deployment?
    primarykey
    data
    text
    <p>I'm not going to make this into a Rails vs Framework X discussion, there's plenty of those already. After seriously contemplating what framework I'm going to use for my next deployment, I decided it's very difficult to pass up the out of the box REST exposure Rails gives you for minimal work back. This is something that requires slightly more work in Django, and considering I'm putting mostly emphasis on the API portion of the app, Rails makes more sense this time around. Considering how important it is for me to write an app that contains heterogeneous clients (iphone/android/tablets) that can access (not just web browsers), I need to be able to build RESTful APIs with minimal resistance from whatever framework I'm using.</p> <p>My question is, is Rails ready to handle not a Twitter sized app, but something that does roughly 75,000 unique hits a day? Does Ruby 1.9.1 really improve things? There's plenty of nightmare stories and equally as many success stories depending on who you ask. Joel Spolsky (one of the founders of stackoverflow.com), <a href="http://www.joelonsoftware.com/items/2006/09/12.html" rel="nofollow noreferrer">believes Ruby itself is just not ready for prime time</a> because it's still considerably slower than other interpreted languages. I'm not worried about getting to Twitter's size (that's a problem I wish to have one day), but on the same token, I do have a site with an average of 75,000 unique users a day. I'm wondering what kind of scaling issues I'll run into by deciding to use Ruby 1.9.1 + latest Rails (CPU costs + memory footprint) as part of my API stack vs. just taking the time to actually do a little extra work in Django to build a RESTful API. As Joel mentions in his article, I don't want to buy 100 servers when I can buy 10. I would love to be convinced as to why Rails is now ready to meet my requirements.</p>
    singulars
    1. PO
      singulars
      1. PTAnswer
    1. This table or related slice is empty.
    1. PTQuestion
    1. USrandombits
    1. USrandombits
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PO
      singulars
      1. PTAnswer
    2. PO
      singulars
      1. PTAnswer
    3. PO
      singulars
      1. PTAnswer
    1. VO
      singulars
      1. POIs Ruby 1.9.1 actually ready and faster for a new Rails deployment?
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. POIs Ruby 1.9.1 actually ready and faster for a new Rails deployment?
      1. This table or related slice is empty.
      1. VTUpMod
    3. VO
      singulars
      1. POIs Ruby 1.9.1 actually ready and faster for a new Rails deployment?
      1. USStéphan Kochen
      1. VTFavorite
    1. COMaybe you should also consider Rubinius (http://rubini.us/) I believe the aim of Rubinius is a fastar and more scaleable Ruby implementation.
      singulars
      1. POIs Ruby 1.9.1 actually ready and faster for a new Rails deployment?
      1. USadamse
    2. COAs a side note, Rails was still in its infancy back in 2006 when Joel wrote that article. Back then fcgi was the way to go. Additionally most of twitters problems weren't about rails is slow, it was rather rails can access only one database. Sure they used plain sql, but any abstraction layer adds overhead regardless of the language used. When you put everything into perspective even if ruby 1.9.x is twice as fast, the overall application speed will only increase slightly.
      singulars
      1. POIs Ruby 1.9.1 actually ready and faster for a new Rails deployment?
      1. USvise
    3. COBesides Django, there is also web2py, as far as Python-based frameworks go; the author designed web2py to include both django features, and rails conveniences.
      singulars
      1. POIs Ruby 1.9.1 actually ready and faster for a new Rails deployment?
      1. USCaleb Hattingh
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload