4 ms·

Check his previous posts, he does lots of work on backend speed. If you put all that advice into one post, it would be pretty overwhelming.

• some1else 11y ago
  For anyone that's interested, here's a guide on scaling Ruby servers to 1000RPM, written by the same author: http://www.nateberkopec.com/2015/07/29/scaling-ruby-apps-to-1000-rpm.html http://www.nateberkopec.com/2015/07/29/scaling-ruby-apps-to-....
  • praseodym 11y ago
    Is it me or is 1000 requests per minute a laughable goal? That's 16.6 requests per second, i.e. 60ms per request _without any parallisation_. I'd expect any unoptimised app to be able to reach that goal.
    • aevv 11y ago
      Maybe if you read the first paragraph you'd find out
    • MichaelGG 11y ago
      Article is actually quite good, but it seems Rails is really slow. Twitter 2007 is said to be at 300ms/req. Others come in around 100ms. So it would seem that you don't get 16RPS without some effort.