4 ms·
It's easy to turn off: remove_action('init', 'wp_cron'); Then just set up your own real cron job to run the `wp-cron.php` script however often you'd like.
by chrisguitarguy 13y ago
It's easy to turn off:
remove_action('init', 'wp_cron');
Then just set up your own real cron job to run the `wp-cron.php` script however often you'd like.
> If your site gets a large influx in traffic the server runs wp-cron for every page hit and further slows things down.
Which involves a single database hit and a `foreach` loop. Or, if you're using an external object cache (memcached, APC, etc), no DB hits.
Probably not as dire a situation as it seems. This...
> If your site gets no traffic then it doesn't run at all.
...is a huge problem.
- Pengwin 13y ago> > If your site gets no traffic then it doesn't run at all. >...is a huge problem. Why? If you are relying on things to happen at an exact time, them you should know not to use wp-cron. However, for the scope of internal wordpress tasks that don't need to happen every load, I don't see any problem with it happening when wordpress is prodded eventually, and the time it was scheduled to run at has passed.