Size a server for a WooCommerce store

Stores are database-bound far more often than they are CPU-bound. Sizing follows the catalogue and the order history, not the visitor count.

Where the resources go

Memory

Database working set, PHP workers and an object cache. The first thing to run short.

Storage

Product images and order history, both of which only grow.

CPU

Checkout, search and admin reports. Bursty rather than sustained.

Which upgrade first

1. Add memory and an object cache before adding vCPU.
2. Add storage before the disk passes 80 per cent.
3. Add vCPU only when checkout latency rises while memory is still free.