WP‑Cron Overhead on Low‑Traffic WooCommerce Sites: Is Disabling Worth It?

WP‑Cron Overhead on Low‑Traffic WooCommerce Sites

WooCommerce schedules tasks—subscription renewals, email notifications, database cleanup—via WordPress’ WP‑Cron system. On a store with few daily page views, each request can trigger a cron run, adding CPU cycles that may inflate hosting fees. Disabling WP‑Cron and delegating task execution to a real system cron promises lower overhead, but the trade‑off is uncertain: will scheduled events be delayed or missed, especially for extensions like WooCommerce Subscriptions that rely on WP‑Cron?

Key uncertainties include the actual CPU cost per page view, the impact of disabling WP‑Cron on critical order processing, and whether a 5‑minute system cron reliably covers all scheduled tasks without gaps.

What is the measurable CPU overhead per page view when WP‑Cron is enabled on a low‑traffic WooCommerce store? Under what traffic patterns does disabling WP‑Cron lead to missed or delayed subscription renewals? Does a system cron running wp‑cron.php every five minutes guarantee that all WooCommerce scheduled tasks execute reliably, or are there edge cases where tasks still fail?