3 ms·
Not sure what your website is doing, but here's a quick thought exercise: If you serve a page in 10s, then you can serve 259'200 pages/month. render_time
by AYBABTME 9y ago
Not sure what your website is doing, but here's a quick thought exercise:
If you serve a page in 10s, then you can serve 259'200 pages/month.
render_time page_view/month
10s 259'200
9s 288,000
8s 324,000
7s 370,285
6s 432,000
5s 518,400
4s 648,000
3s 864,000
2s 1,296,000
1s 2,592,000
So like, think 1 million views per month with 2s render time.
This is obviously skipping over a ton of details, but it's a good rule of thumb.
- tgtweak 9y agoWebsite traffic can be vary heavily during some parts of the day depending on demographics. It's good practice, unless you know that traffic profile, to inflate by 2-3x your average page views per second over any time period larger than an hour. In addition to this, one pageview may produce many requests. Both of these need to be profiled before you can estimate reasonably how much traffic a webserver can handle given it's current resources. There are some good benchmarking tools that will load the entire page, including all it's resources, and produce a more accurate load measure in terms of r/s. As a side note, those $5 vultr instances can handle a surprising amount of static requests per second using nginx.
- deleted 9y ago[deleted]