4 ms·

http://www.readwriteweb.com/cloud/2011/04/twitter-drops-ruby-for-java.php http://www.readwriteweb.com/cloud/2011/04/twitter-drops-ruby...

astrodust 15y ago
You should be so lucky as to have to take something to Twitter-scale. I worry that if they went hand-rolled assembly, everyone would be jumping in that bandwagon.
- gaius 15y ago
  Twitter is actually not that high-volume. They peak at 6000 messages/sec and average much lower (http://blog.twitter.com/2011/03/numbers.html http://blog.twitter.com/2011/03/numbers.html). Meanwhile Tibco will sell you a device doing 100,000 messages/sec sustained (http://www.tibco.com/products/soa/messaging/messaging-appliance/default.jsp http://www.tibco.com/products/soa/messaging/messaging-applia...). There are plenty of people working on systems more scaley than Twitter.
  - orcadk 15y ago
    That's not really a fair comparison however. There's an non-negligible difference between just crunching messages, and then distributing said 6k messages/sec into a directed graph of users. Those 6k messages/sec is just the input, the output is far greater.
    - gaius 15y ago
      That is what RV does.
- moonboots 15y ago
  Better brush up on x86
donw 15y ago
I've downvoted you for providing a worthless answer. The poster asked for similar resources on scaling Rails up; maybe something like https://github.com/blog/117-scaling-lesson-23742 https://github.com/blog/117-scaling-lesson-23742 or http://axonflux.com/building-and-scaling-a-startup http://axonflux.com/building-and-scaling-a-startup would have been useful. I sincerely doubt that the top-poster has Twitter-level problems or resources. He may have a Rails site that's crapping out under load, and needs resources for optimizing both application performance and database access. "Just move everything to Java" is a meaningless answer. It doesn't help him at all, not unless he's got a year and change to retrain/rehire his engineers and completely rebuild his application.

astrodust 15y ago

You should be so lucky as to have to take something to Twitter-scale. I worry that if they went hand-rolled assembly, everyone would be jumping in that bandwagon.

gaius 15y ago
Twitter is actually not that high-volume. They peak at 6000 messages/sec and average much lower (http://blog.twitter.com/2011/03/numbers.html http://blog.twitter.com/2011/03/numbers.html). Meanwhile Tibco will sell you a device doing 100,000 messages/sec sustained (http://www.tibco.com/products/soa/messaging/messaging-appliance/default.jsp http://www.tibco.com/products/soa/messaging/messaging-applia...). There are plenty of people working on systems more scaley than Twitter.
- orcadk 15y ago
  That's not really a fair comparison however. There's an non-negligible difference between just crunching messages, and then distributing said 6k messages/sec into a directed graph of users. Those 6k messages/sec is just the input, the output is far greater.
  - gaius 15y ago
    That is what RV does.
moonboots 15y ago
Better brush up on x86

donw 15y ago

I've downvoted you for providing a worthless answer. The poster asked for similar resources on scaling Rails up; maybe something like https://github.com/blog/117-scaling-lesson-23742 https://github.com/blog/117-scaling-lesson-23742 or http://axonflux.com/building-and-scaling-a-startup http://axonflux.com/building-and-scaling-a-startup would have been useful. I sincerely doubt that the top-poster has Twitter-level problems or resources. He may have a Rails site that's crapping out under load, and needs resources for optimizing both application performance and database access. "Just move everything to Java" is a meaningless answer. It doesn't help him at all, not unless he's got a year and change to retrain/rehire his engineers and completely rebuild his application.