Great for short term use

  • melinahein

    (@melinahein)


    1 month, 1 week ago

    The plugin was great for short term use to figure out unused options from old plugins after clicking through each page. It really helped to reduce autoloaded options.
    When letting it run along for a while as suggested, though, it seems that its database saves were so large it caused our database to use up all the RAM and make our site unusable. So beware of that and only use it for a few days.
    Edit: The Developer reached out immediately and is working on the issue. Great support!

    • This topic was modified 1 month ago by melinahein.
Viewing 4 replies - 1 through 4 (of 4 total)
  • Plugin Author Taco Verdonschot

    (@tacoverdo)

    1 month, 1 week ago

    Hey @melinahein,

    Thanks for your review! I’m happy to hear that you found value in the plugin. And I’m sad to hear it caused problems in the long(er) run.

    I’d like to better understand the situation you ended up in. To do so, it would be helpful to have a rough idea of the size of your site, database and number of options. Is that information you can share here, or through a private message?

    Thanks,
    Taco

    Plugin Author Taco Verdonschot

    (@tacoverdo)

    1 month ago

    Hey @melinahein,

    Ahead of your reply, we have already identified areas for improvement. You can see them in this pull request: https://github.com/ProgressPlanner/aaa-option-optimizer/pull/61.

    If you have any other pointers for us, please comment on that pull request or create a new issue on our GitHub repo: https://github.com/ProgressPlanner/aaa-option-optimizer/issues/new/choose.

    Thanks,
    Taco

    Thread Starter melinahein

    (@melinahein)

    1 month ago

    Hey there @tacoverdo 🙂
    Thank you for reaching out and working on the issue, I appreciate it!
    Our site is pretty large, with about 150 published pages and 120 published posts. The database is around 700MB with ~700 entries for options.

    From what I could trace back, I think your PR already tackles the most important issue. Unfortunately, I no longer have the exact database call that was taking up performance, but it was definitely a get_option call. So preventing it from being called early on should do the trick.

    Greetings,
    Melina

    Plugin Author Taco Verdonschot

    (@tacoverdo)

    1 month ago

    Thanks for your response @melinahein! We’ll move forward with this PR.

    If you, now or in the future, have any other suggestions, don’t hesitate to reach out, please.

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

You must be logged in to reply to this review.