Cost Analysis: TripAdvisor's and Pinterest's costs on the AWS cloud
highscalability.com
highscalability.com
700k requests per minute is ~12k requests per second.
I've had a sustained 4k-5k on a single un-optimised instance of nginx.
TripAdvisor pages are obviously hugely more complex but a lot of the processing will be happening in the middle tier / back end servers. Most of these front-end requests should be trivially cacheable - static content served to anonymous users, images, CSS and the like.
TA java code (used to at least) store every location in a giant location tree in each server. "Location" includes things like continents and countries and towns and ice cream stores and hotels. Just loading in that much data and creating that many objects took ~10 minutes in part because they insisted on writing their own serialization code but didn't bother to do a good job.
And now that I look again, I realize "they" aren't even connected with TA or Pintrest, just a person who has a somewhat shinier AWS cost calculator.
The rule of thumb in the UK, at least, is to double an employee's salary to get the total cost of employing them.