Start with observed demand and an explicit assumption
Capacity planning is not a count of WordPress installations. Record the workload that matters: concurrent uncached activity, processing jobs, storage and the business functions that must remain responsive. Where measurements are absent, label your inputs as assumptions. The worksheet below shows arithmetic headroom around an entered baseline; it does not simulate a server, benchmark Cloudways or determine a safe production configuration for your application.
Keep peak and ordinary behavior separate
A fictional portfolio might be quiet most days but run a large scheduled import every week. Averaging that activity across a month hides the period that can cause trouble. Compare like-for-like time windows and document what was happening during each measurement. Caching, logged-in requests and database work can change the relationship between visitors and resource use, so a simple visit count should not be converted directly into a hardware promise.
Understand what the calculation says
If a measured baseline is 60 units and you apply an illustrative 25 percent planning margin, the arithmetic target is 75 units. The margin is your assumption, not a provider recommendation or a guarantee against failure. The calculation says nothing about whether CPU, memory, disk or another service is the constraint. Use it to make a discussion transparent, then validate the actual bottleneck and available configuration through representative evidence.
Connect capacity to recovery and cost
Check the scaling procedure and the route back before choosing a larger configuration. Disk and provider constraints can make reversal more involved than expected. Also consider whether separating a busy client is more appropriate than enlarging a shared server. The correct next action may be application investigation, workload scheduling or a different ownership arrangement. Do not let a neat worksheet result make an uncertain operating decision look settled.
Sources used for this page
These records support the facts and comparisons above. Merchant-controlled records are labelled so you can separate product claims from independent evidence.
- Cloudways provider-specific scaling and disk restrictions — Merchant documentation · support.cloudways.com · Merchant-controlled · checked 2026-09-21
- Cloudways distributing sites across servers — Merchant documentation · support.cloudways.com · Merchant-controlled · checked 2026-09-21
- W3C guidance for our original worksheet labels — Standards and certification reference · w3.org · Publisher independence not verified · checked 2026-09-21