The linked SO answer is fairly dated (2011), Twitter is able to handle bursts of up @140K req/s (with Scala) as of last year[1]
Assume Rails has improved hugely since then, 600 req/s over 180 instances is absolutely abysmal performance O_o
I'd expect Rails to clock in well under 300ms per request now, and looking at Basecamp's site[2], that seems to be the case, impressively snappy page loads (if caching the kitchen sink and not hitting live Rails stack then we'd need to look at a different example, but this site has pretty much optimal load time).
Assume Rails has improved hugely since then, 600 req/s over 180 instances is absolutely abysmal performance O_o
I'd expect Rails to clock in well under 300ms per request now, and looking at Basecamp's site[2], that seems to be the case, impressively snappy page loads (if caching the kitchen sink and not hitting live Rails stack then we'd need to look at a different example, but this site has pretty much optimal load time).
[1] https://blog.twitter.com/2013/new-tweets-per-second-record-a...
[2] https://basecamp.com