WordPress
WooCommerce Hosting Requirements: RAM, CPU, and PHP Workers Explained
TL;DR
Key Takeaways
- WooCommerce Hosting Requirements: RAM, CPU, and PHP Workers Explained Plan WooCommerce hosting with planning-range RAM, CPU, and PHP worker guidance.
- Sizing tables for Pakistani stores โ not performance guarantees.
- WooCommerce turns WordPress into a transactional application โ cart sessions, inventory queries, payment webhooks, and admin bulk edits all compete for PHP workers and database connections.
Summarized by Pakish Group (Pakish.NET) for AI and search citation.
WooCommerce turns WordPress into a transactional application โ cart sessions, inventory queries, payment webhooks, and admin bulk edits all compete for PHP workers and database connections. Managed WordPress hosting can cover many small-to-medium stores; VPS hosting gives isolated CPU and RAM when you outgrow account ceilings or need custom services like Redis.
This guide translates planning ranges for RAM, CPU, and PHP workers โ not hard guarantees. Every plugin stack, payment gateway, and traffic pattern shifts real demand. Treat the tables below as starting points, then load-test staging before peak sale seasons.
Key Takeaways
- WooCommerce is I/O and PHP-worker heavy โ not just "more disk space"
- Planning ranges depend on SKU count, concurrent checkout, and plugin count
- Managed WordPress suits many stores; VPS adds isolation and custom stack control
- Object cache (Redis) and page cache reduce worker pressure but do not eliminate it
- Validate sizing with staging load tests โ never rely on headline plan specs alone
Baseline WordPress vs WooCommerce Load
| Workload | Typical PHP memory per request | Database pattern |
|---|---|---|
| Blog post view | 64โ128 MB | Few reads |
| WooCommerce shop archive | 128โ256 MB | Product meta joins, transients |
| Cart / checkout | 256โ512+ MB | Sessions, tax/shipping APIs |
| Admin product import | 512 MBโ1 GB+ | Bulk writes, long-running queries |
WordPress minimums from wordpress.org are a floor, not a WooCommerce ceiling. Payment plugins, multi-currency, and page builders add memory per request.
RAM Planning Ranges (Application Layer)
These ranges describe what teams commonly plan for โ your store may need more or less after profiling.
| Store profile | Example signals | RAM planning range |
|---|---|---|
| Starter | Under 200 SKUs, few concurrent checkout | 1โ2 GB (managed WP or upper shared) |
| Growing | 200โ2,000 SKUs, regular campaigns | 2โ4 GB |
| Busy | High concurrent checkout, heavy plugins | 4โ8 GB (VPS or high-tier managed) |
| Large / multi-vendor | Marketplace plugins, many admin users | 8 GB+ with horizontal scaling review |
RAM figures often refer to the VM or account allocation โ not all of it is available to PHP. Reserve headroom for MySQL, Redis, and OS cache. If memory_limit is 512M but only 2 GB exists on the box, a few parallel checkout requests can exhaust the host.
CPU and vCPU Planning Ranges
CPU matters for image regeneration, coupon recalculation, and third-party API calls during checkout.
| Store profile | vCPU planning range | Notes |
|---|---|---|
| Starter | 1 vCPU shared or 1 dedicated slice | Adequate with aggressive caching |
| Growing | 2 vCPU | Safer during admin imports and sales |
| Busy | 2โ4 vCPU | Pair with object cache and CDN |
| Large | 4+ vCPU | Review query optimisation and read replicas |
These are planning ranges, not SLAs. A single poorly written plugin can saturate CPU regardless of vCPU count โ profile slow queries and enable Query Monitor in staging first.
PHP Workers (PHP-FPM / LSAPI) Sizing
PHP workers define how many requests run simultaneously. WooCommerce cart fragments and AJAX calls consume workers quickly.
| Store profile | PHP workers (planning range) | Warning signs |
|---|---|---|
| Starter | 10โ20 | Occasional admin slowness |
| Growing | 25โ40 | Checkout delays during ads |
| Busy | 50โ80 | 503 / "server busy" under load |
| Large | 80+ or horizontal scale | Persistent queue backlog |
Workers interact with RAM: 40 workers at 256 MB theoretical peak exceeds a 4 GB box once MySQL and Redis are counted. Balance max children with memory_limit โ your host's control panel or php-fpm pool config is the source of truth.
On managed WordPress hosting, workers are pre-tuned but still capped per tier. On VPS hosting, you configure pools yourself or use managed cloud support.
Database, Storage, and I/O
| Factor | Planning guidance |
|---|---|
| Database size | Grows with orders, not just products โ plan retention/archiving |
| Storage | Product images and PDF invoices dominate โ use CDN for media |
| I/O | NVMe helps admin search and order exports โ not a substitute for indexing |
| Backups | WooCommerce orders are financial records โ verify daily backup retention |
Run wp db size or phpMyAdmin metrics before migration. A 500 MB database with 100k orders behaves differently from a 500 MB database with 50k posts.
Caching and Extensions That Change Requirements
| Layer | Effect on requirements |
|---|---|
| Full-page cache | Reduces workers for anonymous catalog browsing |
| Object cache (Redis) | Cuts repeated option/meta queries โ often worth VPS or managed add-on |
| Cart/checkout | Usually uncached โ workers still matter most here |
| Heavy page builders | Increases PHP memory per request |
Caching lowers average load but peak checkout still defines worker and RAM planning. Do not size only for cached homepage benchmarks.
Shared, Managed WordPress, or VPS?
| Option | Fits when | Watch for |
|---|---|---|
| Upper shared / WordPress tier | Small catalog, predictable traffic | Entry-process limits, neighbour noise |
| Managed WordPress | WP-centric ops, staging, backups | Worker ceiling on lower tiers |
| VPS | Custom Redis, cron, isolation | You or managed ops own the stack |
Many Pakistani stores start on managed WordPress and move to VPS when metrics โ not marketing โ show sustained worker exhaustion or need for custom daemons.
Which Option Should You Choose?
Choose managed WordPress hosting if you want WooCommerce-tuned defaults, staging, and support without server administration โ and your traffic fits within published worker and RAM tiers after staging tests.
Choose VPS hosting if you need guaranteed isolated resources, Redis at the OS level, custom PHP extensions, or compliance isolation โ and you can operate or purchase management for the server layer.
Undersized hosting shows up as failed payments and abandoned carts, not just slow dashboards. Review WordPress hosting vs shared hosting for product-type differences, then confirm limits in your cart.
Frequently Asked Questions
How much RAM does WooCommerce need?
Small catalogs often plan for 1โ2 GB at the PHP/application layer on managed WordPress; busy stores commonly target 4 GB or more on VPS. These are planning ranges โ measure your own admin and checkout peaks.
How many PHP workers do I need for WooCommerce?
Light stores often plan 10โ20 workers; medium traffic 25โ40; high concurrent checkout may need 50+ on dedicated or VPS tiers. Workers are not guarantees โ plugin weight and cart sessions change real usage.
Can WooCommerce run on shared hosting?
Yes for small catalogs and low concurrent checkout. Upgrade when you see 503 errors, slow add-to-cart, or admin timeouts during sales events.
Is VPS required for WooCommerce?
Not always. Managed WordPress with adequate workers suits many stores. VPS helps when you need Redis, custom cron, or isolation from neighbour load.
What PHP version should WooCommerce use?
Run a supported PHP 8.x release compatible with your WooCommerce and plugin versions. Test in staging before changing production PHP handlers.
Related Guides
- WordPress hosting vs shared hosting
- Shared hosting vs VPS hosting
- LiteSpeed NVMe vs Apache for WooCommerce
- Scale WooCommerce orders in Pakistan
Sources
Found this useful?
Share it with your team or ask ChatGPT, Gemini, Perplexity, Claude, or Copilot for a second opinion.