We’re running 20+ installations of Pro in 5 multisite installations on a dedicated server.<\/p>\n
Our hosting support team has identified processes run by the calendar that cause the server to run out of 16 GB of memory:<\/p>\n
I have also checked the script execution logs from the same time period and noticed that at several points, a few of your applications have executed multiple simultaneous wp-cron.php requests. For example, all of these requests were started in only 5 minutes: <\/p>\n
(he then listed them)<\/p>\n
There are multiple wp-cron requests which are executed on a constant basis and appear to be the main cause for the large consumption of memory.<\/p>\n
These tasks are part of the Events Calendar plugin which is present in each of the installations I tested. What we can suggest you to try for now is to try increasing the time period needed for execution of these events. There are several ways to do that.<\/p>\n
The first one is to make sure that each cron process cannot run more than once during the predefined cron lock timeout period. Such value can be defined by adding this code in the wp-config file of each of your WordPress installations:<\/p>\n
Code:
\ndefine( ‘WP_CRON_LOCK_TIMEOUT’, 120 );<\/p>\n
The shown example sets this period for 2 minutes, but you can modify this value to a larger one.<\/p>\n
NOTE: We tried this, and the calendar hangs in the dashboard. It stopped hanging after we reversed this solution.<\/p>\n
THIS ALSO WAS SUGGESTED:<\/p>\n
Another approach you may take is to enable the alternate cron functionality of WordPress:<\/p>\n
Code:
\ndefine( ‘ALTERNATE_WP_CRON’, true );<\/p>\n
After that you can navigate to the Cron jobs tool in cPanel and define the timeframe at which the wp-cron script to be executed.<\/p>\n
QUESTION: Do you recommend this solution? Will it also cause performance issues in the dashboard? Or do you have another solution?<\/p>\n","protected":false},"template":"","class_list":["post-1324328","topic","type-topic","status-closed","hentry"],"yoast_head":"\n