@andreas-2013 All preload is doing that it visit’s your site programmatically. So, it will take the same amount of resources if you visit the pages manually.
The preload doesn’t run as a single task. Once the PHP script reaches the time limit (max_execution_time), the remaining URLs are scheduled to preload later. We do see the possibility and increase the time limit to 30 minutes. What you have done is that increase the interval between batched preload tasks.
If you don’t want to run a single preload task for 30 minutes, then you can reduce it by defining a constant WP_OPTIMIZE_SET_TIME_LIMIT to your desired seconds.
Hi Venkat Raj,
thank you for your reply!
I’m not sure, if I understand right the process of preloading. When the limit of 30 minutes is reached, the preload stops automatically, and afterwards it starts again with the remained URLs, and so on? But could you explain me, please, the meaning of the attaced graphics? Why is the use of memory increasing up to 7.5 GB? What will happen, if I change the time limit to 15 minutes?
@andreas-2013 When you reduce the time limit, the usage spike will be for short periods rather than long. One possible explanation for high memory usage is that if your site uses lots of different set of scripts/styles in each pages, then minify assets will be created for those sets separately.
Could you please deactivate/activate the WP-Optimize and see if that fixes issue?
That said, it seems system (disk I/O, network communication, etc) too take lot of resource apart from WP-Optimize’s PHP process?
@webulous Could you explain, please, how and where to use WP_OPTIMIZE_SET_TIME_LIMIT ?
@andreas-2013 Please add following line in your wp-config.php file
define('WP_OPTIMIZE_SET_TIME_LIMIT', 300);
This will result in 5 minute preload chunks
