Re:Twitter survives election after Ruby-to-JVM move
by jshen on Thursday November 08, 2012 @01:54AM
(#4756750)
It's not primarily about the size of traffic, but the ability or inability to cache. At work we serve a ton of traffic with MRI ruby and 3 small VMs. Most requests are served by varnish and never hit the ruby stack. Most people do a terrible job at caching (edit: I'm not saying that twitter is bad at caching).
[ Parent
| on HN ]
Re:Twitter survives election after Ruby-to-JVM move
by kayoone on Thursday November 08, 2012 @02:00AM
(#4756764)
Twitter is hugely write intensive and needs realtime data, so their caching needs are probably vastly different from yours.
Re:Twitter survives election after Ruby-to-JVM move
by jshen on Thursday November 08, 2012 @02:04AM
(#4756775)
That was my point. Their caching needs are vastly different from almost everyone!
Re:Twitter survives election after Ruby-to-JVM move
by bryanlarsen on Thursday November 08, 2012 @05:37AM
(#4757235)
Agreed. I've got a page that takes 20 seconds to render on a dedicated fast machine. I could spend some time optimizing it, but even then it would still be slow. However, it's cacheable so I can fix performance problems with a simple post-deploy script. We can't do that for every page, but it's awesome when we can.