This topic has 21 replies, 2 voices, and was last updated 2 years, 5 months ago ago by Olga Barlow
Hello,
We are doing some database cleanup and our developer has turned up an oversize autoload row in our wp_options (see screenshot below). It seems to contain the XStore demo templates. Our developer states:
“This is an oversized wp_options autoload row. It contains templates from XStore. They should offer a way to remove or set it to not autoload such a huge payload 10x a maximum row size. Wastes RAM. Causes object caching key rejections.”
Can you please advise how we can fix this??
Thanks for your assistance.
Hello,
System loads that only if you click the XStore Studio icon to import studio sections. Anyway, provide us with WP Dashboard and FTP access to your site and we’ll disable autoloading.
Regards
Hello,
That would be appreciated. Please let me know what you have changed, so I can adjust in the future if needbe.
Thank you for your assistance.
Ben
Hello,
Thank you. I have passed the issue to our developers. I’ll inform you once they fix the problem.
Regards
Thank you for your help with this. I’ll watch for your message back.
Ben
Hello,
Yes, sure. We need 1-2 days for this.
Regards
Hello,
Fixed. Check now, please.
Regards
Good morning,
Still seems to be there……
Please advise.
This is the query:
SELECT
‘Autoload KB’ as name, ROUND( SUM( LENGTH( option_value ) ) / 1024 ) as size, null as autoload
FROM wp_qfda_options
WHERE autoload = ‘yes’
UNION
SELECT ‘Autoload count’, count( * ), null as autoload
FROM wp_qfda_options
WHERE autoload = ‘yes’
UNION (
SELECT option_name, length( option_value ), autoload
FROM wp_qfda_options
WHERE autoload = ‘yes’
ORDER BY length( option_value ) DESC
LIMIT 20
)
UNION (
SELECT option_name, length( option_value ), autoload
FROM wp_qfda_options
WHERE autoload = ‘no’
ORDER BY length( option_value ) DESC
LIMIT 20
)
also wondering about “et_multiple_single_product” is that a needed autoload row? I understand some may be necessary for plugin performance.
Good morning,
Any progress with this??
FYI we are trying to get decrease our autoloads, and that et_studio_data is a big one. Our hosting provider, WP Engine recommends keeping autoloads to less than 800K for object caching to work properly: https://wpengine.com/support/wp-engines-object-caching/
We have had to disable object caching until we can get our autoloads reduced.
Thanks for all of your help.
Ben
Hello,
Sorry for the delay in answering. Could you, please, provide us with phpMyAdmin access to your DB. We need to make code improvements and check if that works.
Regards
Good morning,
I will need to set you up as a user on our WP Engine account. Can you please provide email address to send the invitation?
Thanks,
Ben
Hello,
It redirects us to this form https://prnt.sc/O0wiGGxJdOGX
What credentials should we use there?
Regards
I believe that you must set your own password to access this. Please provide me with an email address so that I can have an invitation sent to you, so you can establish credential.
Ben
OK, lets’s do it like this. I have established credential for you.
Hello,
Check autoload now.
Regards
Good morning,
The large row is gone – thank you!
Can you tell me, with this change persist in future releases of the theme?
Regards,
Ben
Hello,
Yes. We’ll disable autoload for the studio in the next update.
Regards
Hello,
Perfect! Thank you for your help taking care of this!
We appreciate the support.
Regards,
Ben
Hello,
You are welcome.
Regards
Tagged: autoload, et_studio_data, oversize, templates, woocommerce, wordpress
The issue related to '‘Oversize wp_options autoload row – et_studio_data how to fix?’' has been successfully resolved, and the topic is now closed for further responses