Question About DB Options

Hello Simon,

Thank you for your message and for using our plugin.

That option is created by the Freemius SDK, which we use in our plugin. We have already got in touch with Freemius and will get back to you with an update shortly.

In the meantime, can you please tell us more on what makes this setting “one of the larger offenders”?

Looking forward to hearing from you.

Good Morning @robert681

I apologize for the delayed response here! I did not get the email notification I would’ve expected form WordPress.

I appreciate you reaching out to the Freemius team for us here!

As far as what I mean by “Large Offender:”

WP Engine (where our site is hosted) recommends we have the WP Options DB Autoloaded data under 800k bytes. When we first started cleaning things up we were at 2.8m bytes. So quite a bit over.

We were able to turn off options of sizes: 470k bytes (a HUGE offender), 250k bytes, 245k bytes. etc. Since that cleanup started we have gotten it down to 990k bytes, so we are getting close.

They were all relatively common options (from and old Woo POS plugin and Yoast), however, because of the rather large size (and age) of our site (it’s a very active ecommerce store) those options tables grew very large.

At this point, our “largest offender” in table size is that fs_accounts table coming in at 101,493 bytes.

If it is safe to turn off that options table autoloading we will get much closer to our goal here!

If you need any more information from me on that “large offender” language please just let me know!

Thanks so much!

-Simon

Thank you very much for the detailed explanation @simonbbs

After discussing this with Freemius, it turns out that someone else has already reported this problem. I’m copying part of Freemius’ response below:

I wish it was as easy as setting the autoload to false – if that was the case we would have done that a long time ago. The thing is that we are storing all the settings in a single option record and some of the settings are required on every PHP load, so setting the autoload to false will not resolve it, the option will be loaded anyway but in a separate DB query (less performant).

The good news is that it seems there is a plan to split the settings, and not have them all on autoload.

If you would like to follow this issue you can do so on Github.

I am sorry I do not have a definitive answer, or a solution for you. However, it seems this problem will be solved some time soon.

Should you require any further information please do not hesitate to ask.

Have a great day.