Evergreen: Autoload performance issue

  • tommy83

    (@tommy83)


    1 year, 5 months ago

    Hello,

    we talked to some developers and also our hoster confirmed that issue after doing code and performance profiling of your plugin:

    This plugin adding very big autoload data to db. Its 14x bigger as the second biggest one.
    If we disable your plugin or set autoload to OFF the problem of performance is gone.

    We have 32 cores, 256G RAM and a very powerfull dedicated managed server with nvmes and latest mysql version (+mariadb).


    We have found a “compress” option in your plugin. But you wrote about this option here this feedback:
    https://ww.wp.xz.cn/support/topic/wp_option-table-for-input-with-autoload-ws_menu_editor/

    Janis Elsts

    (@whiteshadow)

    3 years, 8 months ago

    It’s not on by default because there’s a performance trade-off here. A compressed option takes up less space, but the plugin needs to decompress it before it can be used, which takes more time. There’s a risk that this additional time could exceed the time that was saved by loading less data from the database, which means enabling this option could actually decrease overall site performance.

    I’m not sure how high that risk is; it will probably vary depending on the server.

    So finally the result is:
    compress: will solve autoload problem and will solve server load issue based on this problem.
    But from that moment you will have another/new server load compress: The whole website is getting slower, because your plugin cause now another slow page problem based on de-compressing data.

    I understand this correct, or it was a joke? 😉 Sorry for that words, but i dont belive that is true.
    How to improve your plugin performance please?

    BR
    Tommy

Viewing 1 replies (of 1 total)
  • Plugin Author Janis Elsts

    (@whiteshadow)

    1 year, 5 months ago

    Technically, there is a trade-off. There must be one since decompressing data takes non-zero time. However, in practice, it could be a tiny amount of time. I didn’t notice any slowdown on my own site(s) when enabling compression (though I’ve only done limited testing on that).

    I would recommend measuring performance before and after enabling that option (remember that you need to re-save the admin menu after enabling compression). If the large ws_menu_editor DB entry was actually the root cause of the problem, my guess is that enabling this option would improve overall performance.

Viewing 1 replies (of 1 total)

The topic ‘Evergreen: Autoload performance issue’ is closed to new replies.