Intermediate8 min read
Size a server for a WooCommerce store
What actually consumes resources in a store, and which upgrade to buy first.
Last updated 1 August 2026
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
- Add memory and an object cache before adding vCPU.
- Add storage before the disk passes 80 per cent.
- Add vCPU only when checkout latency rises while memory is still free.
Enable backups before the first real order
Order data cannot be reconstructed from anywhere else. Confirm a restore works while it still costs nothing to get wrong.Was this page useful?
Feedback about article woocommerce-sizing