News for hackers. Stuff that matters.
Re:Rails 3.2 Performance: Another Step Slower by laureny on Tuesday November 26, 2013 @10:30PM (#6806131)
> Twitter was in a nice position to better Ruby in terms of performance, though they chickened out and escaped to Scala.

Actually, they escaped to the JVM, and if their job reqs are any indication, they hire massively for Java engineer positions and hardly at all for Scala ones.

I wouldn't call that chickening out, more common sense.

Rails is great for prototypes and toy apps, but once you start needing scale, it's simply not up to the task.

Re:Rails 3.2 Performance: Another Step Slower by ropiku on Wednesday November 27, 2013 @01:32AM (#6806795)
I work at Twitter. Actually we use very little Java while almost every service is written in Scala.
Re:Rails 3.2 Performance: Another Step Slower by why-el on Wednesday November 27, 2013 @03:26AM (#6807100)
> Rails is great for toy apps

This gets said here a lot. What about GitHub and Shopify, and ...? Are those toy apps?

Re:Rails 3.2 Performance: Another Step Slower by porker on Wednesday November 27, 2013 @03:50AM (#6807161)
I'm curious too how much of each of these is still built on Rails, and how much has been tweaked, tuned and rewritten to be 'inspired' by Rails, but no longer Rails.
Re:Rails 3.2 Performance: Another Step Slower by why-el on Wednesday November 27, 2013 @07:53AM (#6807766)
Good question. I would say it varies, but after all they are mostly likely not changing things dramatically, at least thats what you get from watching talks from both companies[1].

[1] http://www.slideshare.net/jduff/how-shopify-scales-rails-204...

Re:Rails 3.2 Performance: Another Step Slower by twerquie on Wednesday November 27, 2013 @09:05AM (#6808053)
GitHub is still on Rails 2.3 and has not upgraded partially due to performance concerns*

*From an episode of Ruby Rogues with Zach Holman

Re:Rails 3.2 Performance: Another Step Slower by berntb on Wednesday November 27, 2013 @08:10AM (#6807824)
I've browsed this discussion and I must miss something?

You seem to imply Ruby's/Rails' speed matter?

Usually, the DB is the limiting factor in most web applications, few should need to execute more than a few milliseconds of (even) Ruby per page load. That is why people use scripting languages, after all.

Shouldn't this slowdown be a problem in the ORM for this version? I'd look at access patterns for normal requests for the new Rails version and the old. How has the SQL changed?

Sure, Twitter is different since that probably is processor bound.

(Since RoR is a popular framework with lots of eyes, there shouldn't be something simple with e.g. configuring the web server, locking etc.)

Re:Rails 3.2 Performance: Another Step Slower by porker on Wednesday November 27, 2013 @03:48AM (#6807151)
I guess if you wanted Scala programmers (and for the long-term, not just a 3 month contract) you would hire for Java programmers as a) there's a lot more of them so the talent pool is larger, b) teaching a Java guy/gal Scala isn't going to be difficult, and c) they may be cheaper to get (a pure guess)?