Rebuild cache fails when caching huge list

Hi Zion,

what is your current wp & php memory and have you tried to increase it ?

see the plugins ‘about your db’ page – it will show current situation.

Unfortunately because of the way the plugin came about (need to access and sort/filter non wp user fields) it is uncomfortably a memory hog in it’s current form.

If you are at max memory, you could try tweaking the query method – see general settings somewhere. BUT reality is if the site is running close to the max already it’d be safer to look at another option.

I do have plans for a less memory intensive method BUT that will be a while and will probably have less ‘features’ initially.

NB that you do not have too frequent cache rebuild runs else will place unnecessary load on the system.

Hi Anmari,
Thanks for responding back! I’m currently using 3.8.1 and my PHP memory is HUGE, so I’m very hesitant to keep increasing it. Our user base will only grow, and I need something that would be scalable.

Sure, how would I go about tweaking the query method?

I did check the settings and it’s currently stated as follows:
General Settings

• Checked Fetch users directly to save load – for large databases
• Fields and Nice Names had a lot of data that didn’t need to be in the report – so I checked them, hopefully that would help as well

Cache Settings

• Do re-cache on user update is checked
• Re-cache frequency is set to hourly

I changed the cache settings to “do not recache on user update” and “no scheduled autocache” in the hopes that it may reduce some of the load.

With the things I just did, I’ll see if they produce better results.

Ok that didn’t work…

I just ended up deactivating the plugin for now until I can figure out what to do.

Thanks!

Look in your wp-includes for a file named “default-constants.php”. than change the following code

if ( ! defined( 'WP_MAX_MEMORY_LIMIT' ) ) {
		define( 'WP_MAX_MEMORY_LIMIT', 'xxxM' );
	}

change the xxxM to something higher. This worked for me.

Hey @sadninja,

Thanks, that’s exactly what I did previously before. Because our data keeps getting bigger, it’s not great to keep changing that file when our data balloons, especially when I have to update the WordPress core files.

Sadly, I’m running out of ideas. I thought about just parsing the data to the smallest amount of fields needed to populate, but will see how that goes. I’ve been working on a straight up PHP to MySQL hard-coded filterable table as a backup option.