• Resolved oakandrocks

    (@oakandrocks)


    When you started on 2024-10-05 you had 1125 autoloaded options, for 2,126.2KB of memory. Now you have 1000 options, for 3,870.0KB of memory.

    option_optimizer | AAA Option Optimizer | 2,377.91 |on

    How are you optimizing my autoload options if you add your own autoloaded option which literally weights more than twice my previous total autoloaded option weight?

    Resetting data doesn’t clear it either.

    I’m going to try deleting it – i guess?
    This is a bit silly.

    The page I need help with: [log in to see the link]

Viewing 8 replies - 1 through 8 (of 8 total)
  • Thread Starter oakandrocks

    (@oakandrocks)

    Removing from Autoloaded – even though correctly displayed as “removed” in AAA page – still shows in Site Health – Autoloaded

    Thread Starter oakandrocks

    (@oakandrocks)

    Rectification – Removing option_optimizer from autoloaded options will show as removed but will show as enabled if page is refreshed (so probably never removed).

    What should I do?

    Thread Starter oakandrocks

    (@oakandrocks)

    Same thing with the “Delete” option.

    Thread Starter oakandrocks

    (@oakandrocks)

    Had to manually UPDATE wp_options SET autoload = ‘auto-off’ WHERE option_name = ‘option_optimizer’;

    Thread Starter oakandrocks

    (@oakandrocks)

    Correction, even manually setting it doesn’t last.

    Your pos plugin keeps persistence and doesn’t work at removing/disabling autoload.

    MariaDB [wordpress]> SELECT option_name, autoload FROM wp_options WHERE option_name = ‘option_optimizer’;
    +——————+———-+
    | option_name | autoload |
    +——————+———-+
    | option_optimizer | on |
    +——————+———-+
    1 row in set (0.000 sec)

    Plugin Author Taco Verdonschot

    (@tacoverdo)

    Hey @oakandrocks,

    Thanks for reporting this. You’ve stumbled upon a bug in the plugin. Our devs are now aware, and will investigate, resolve and push an update of the plugin. We aim to release this next week.

    Thread Starter oakandrocks

    (@oakandrocks)

    Deleting the plugin gets rid of the issue.

    Plugin Author Taco Verdonschot

    (@tacoverdo)

    Well yes, that’s correct. But, we’re still moving forward to resolve the problem in the plugin. As of next version, it should no longer show this incorrect behavior.

    We’re sorry for introducing this bug, and thank you for reporting it!

Viewing 8 replies - 1 through 8 (of 8 total)

The topic ‘option_optimizer taking more than 50% of the total autoloaded size’ is closed to new replies.