Here’s another example: https://better.boston/@crschmidt/109412294646370820

@crschmidt cites around 112MB over one minute with 7-8 requests per second.

To be clear: that is not much for even a basic cache, e.g. using Nginx, even on a small server. But it will easily crush a basic WordPress/MySQL setup that is exposed to the traffic directly.

For most people running a website with public content I’d recommended not rolling your own hosting. There’s plenty of providers who do this all for you and it’s often cheaper than renting your own server anyway.

If you do want to dive into this, which is fun and interesting, absolutely look into basic caching. It’s not much effort and will very likely safe you major headaches and money.

Trust me, I’ve been doing this for decades. I’ve made most mistakes, hopefully I made each only once. 😅

One of the best “bang for your buck” ways to go is to host your site as static files which works for a large portion of personal sites which don’t have things like comment sections. Static hosting is super scalable and keeps the technical complexity low: no database, no Ruby/PHP/etc.