Venkat Raj

@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?

@dmvisuals There was a compatibility issue with WordPress 6.2 Which is fixed in version 3.2.14. You are still using 3.2.13, Please update

@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.

@edviser Could you please tell me the versions of
WordPress
PHP
WP-Optimize?

Thanks!

@vladimirvuch What theme and plugin you are using for that functionality?

You can send it here: [email protected]

@fkoomek You could use Schedule preloader option and set schedule type as same as cache lifespan

This runs preload whenever the cache is purged.

@lordsnake Could you please share your php error_log file? Thanks You happen to use any CDN?

@jidwictut9 Do you mean .htaccess file in the root? If so, I couldn’t reproduce the issue. WP-Optimize only removes the rules added by it such as browser caching, gzip compression, etc It does that based on comments such as # BEGIN WP-Optimize Gzip compression. If you happen to add your rules between the #BEGIN and #END comments, then this can happen

@formularon Could you please provide more information about your server? Do you use clourflare?
If you would like to discuss this in private, please send email [email protected]

@roow Please follow this article. https://getwpo.com/faqs/how-can-i-get-these-tools/

@jakebb Those files are not useless files, those are used to determine the redirection capability of your server. That said, we are working on a fix to remove the usage of those file.

@formularon I assume, your hosting provider added PHP’s built in function escapeshellarg to disable_functions directive for security purposes.

You can add define('WPO_USE_WEBP_CONVERSION', false); to your wp-config.php file to prevent this.

@goldcrest As said earlier, there is no such feature at this moment. I can think of only one solution for this. Reduce the cache life span to your desired duration

@libergm WP-Optimize is not fully compatible with AMP