These numbers are fine and all, but what really matters is how many requests per second it can do. Combined with response time across a timeline where you gradu

These numbers are fine and all, but what really matters is how many requests per second it can do. Combined with response time across a timeline where you gradually increase the number of clients (fake or real). To observe where your server experiences pain, and watching how it deals with it, and how/if it recovers is super useful. Benchmarking tools to pound your servers are plentyful, and these stats (connection/sec and avg response time) combined with the hardware spec is what makes a good praise or diss of a webserver performance. Maybe you'll never intent do draw a huge load for real. I'm just saying its performance can be measured better than its cpu and ram usage while on low or no load. Even if that is a useful aspect in some sense. Unless this is serverless of course. New ballgame entirely.