Menu

How to size a VPS: the rules of thumb behind an open calculator
📰

How to size a VPS: the rules of thumb behind an open calculator

DEV Community: php·ricco020·1 day ago
#dAfYzbMX
#devto#dev#calculator#peak#average
Reading 0:00
15s threshold

Most "what VPS do I need" answers are a single number with no reasoning. When I built a small open calculator for this, I decided every assumption had to be visible, so anyone can disagree with it. Here are the rules of thumb it uses. They are rules of thumb, not benchmarks.

1. Turn monthly visits into a peak, not an average

Visits are converted to page views at 2.5 page views per visit .

That gives an average rate per second.

The average is multiplied by 4 for steady traffic and by 12 for spiky traffic (launches, newsletters, social).

The server has to survive the peak. Sizing on the average is the most common mistake.

2. CPU: peak rate times cost per uncached request

Assumed CPU time for one uncached request:

Stack CPU-seconds per uncached request

Static site (Nginx / Caddy) 0.002

Node.js app 0.02

Docker containers 0.05

Laravel / PHP app 0.06

WordPress 0.08

WooCommerce 0.15

The result is doubled to leave room for bots, admin pages, cron and updates.…

Continue reading — create a free account

Join HashtagPLUS to read full articles, follow hashtags, vote, and join the conversation.