I don’t have full confirmation that they no longer see out of memory issues, but from logging the memory usage at shutdown it appears that this memory issue has likely been reduced by setting the following option in the get_posts call in cartflows: ‘update_post_meta_cache’ => false Obviously this isn’t ideal as a plugin update will … Read more
Query Monitor is a good way to track what part of WP is chewing up resources. What search functionality are you trying to implement, exactly? It’s very hard to give advice based on a vague question that leaves out relevant details.
WP_Query (or WC_Product_Query) out of memory
Fatal error: Allowed memory size of 268435456 bytes exhausted (tried to allocate 20480 bytes) in
Post SMTP: Fatal error: Allowed memory size … exhausted
How to fix Fatal Error in wp-includes/meta.php after upgrade to PHP 8
This is a perfect use case for Transients. In WordPress, transients are short-lived data objects. By default, they’re persisted to the database using WordPress’ built-in WP_Object_Cache object. However, you can use a variety of caching plugins (Batcache is an outstanding one that works with Memcached) to store Transients in memory. To set a transient, call … Read more
So you’ve tried setting the WP_MEMORY_LIMIT variable in the wp-config.php file, but have you tried .user.ini or .php.ini? Create one of those files (yes, with the period in front) and then use: memory_limit=30M Or whatever value you’re looking for. By default, WordPress is set to 40mb for a single installation, and 64mb for a multisite … Read more
Difference between php memory limit and wp memory limit?
It’s hard to answer this given that each site is most likely different and each server is also configured differently. If these sites are individual WordPress installs then 1GB /30 sites is normal, an absolute bare minimum per site would be 32MB for apc.shm_size, this equals 960MB with no overhead. 32MB is in my opinion … Read more