@kierancalv
The aspect of serialization has beent talked with the developers and is taken into considerations.
From what I see, the options have auto by default.
How recently did you installed the plugin?
We are a cache and optimization plugin. The ideea is that cache is generated, then there will no need to run all the code all over again and be served faster.
Thanks for getting back to me.
The plugin was installed today on this site, but I’ve added it to around 20 sites over the past month as I’ve moved back to using LITESPEED on the Server. It’s only now that I noticed the options issue.
On inspection, the plugin is creating 197 separate options. On sites running WooCommerce and several other plugins, this can push the options table much closer to recommended limits than it needs to be.
I spend a lot of time optimising the options table to improve admin performance, particularly on sites with a large number of resource-heavy plugins. Having this plugin add 197 individual options when they could potentially be stored as a much smaller number of serialised options makes optimisation significantly more difficult.
Ideally, related settings should be consolidated into serialised options rather than being stored as hundreds of separate entries. This would reduce the overall option count, keep the database cleaner, and improve scalability on larger WordPress installations.
@kierancalv I totally agree with you.
Changing how options are saved is something we are looking into and one of the things we are going to change.
I cannot give you a timeline about the change
