How to size a VPS: the rules of thumb behind an open calculator
A developer built a small open calculator for estimating the VPS resources a site needs, making every assumption visible so readers can challenge it. Traffic is converted from visits to page views at 2.5 per visit, then to a per-second rate, scaled by 4 for steady traffic or 12 for spiky traffic. CPU needs are estimated from assumed CPU-seconds per uncached request for stacks ranging from static sites to WooCommerce, doubled for bots, admin tasks and cron, with a page cache cutting PHP stacks to about a third. RAM estimates add per-app and database figures, plus the operating system, peak workers, extras and a 30 percent safety margin. The author warns that disk often runs out silently, recommends real monitoring data over calculator estimates when a site already runs, and suggests 2 vCPU as the comfortable minimum for anything using PHP or a database.
This is an AI-generated summary. ShortSingh links to the original source for the complete article.
Discussion (0)
Log in to join the discussion and vote.
Log in