channel_statics on autoload

  • Resolved sanderrrrr

    (@sanderrrrr)


    2 years, 9 months ago

    Hello,

    when cleaning up my DB the largest file that is on autoload is called ‘channel_statics’.
    I believe this is from your plugin. The filesize is almost 80kb.

    What is this file, does it need to be autoloaded?
    Or can this even be removed?

    Thank you for your advice.

Viewing 10 replies - 1 through 10 (of 10 total)
  • Thread Starter sanderrrrr

    (@sanderrrrr)

    There is another autoload called ‘cron_projects’ (55kb) that is also autoloaded. Is this also your plugin?

    Hi,

    Thanks for using our plugin and reaching out to us.

    Yes, both are from our plugin. Channel_statics can be removed but you will lose the history of your configured feeds (when your feeds were updated and how many products were in your feeds after each update).

    Thread Starter sanderrrrr

    (@sanderrrrr)

    Thank you for letting me know.
    So be default you autoload 2 large (massive) record from the databas?
    2x 50kb added, on every single load, for no clear reason.

    This seems to be really large for what is supposed to be a relatively passive background feed generator.

    Why did you choose for autoload in this case and is there not a better solution to this problem?

    Hi,

    The channel_statics one is not autoloaded, this comes from the plugin code:
    update_option( 'channel_statics', $channel_statics, 'no');

    The cron_projects is indeed autoloaded, we will check if this is really needed. When not we will make the changes in the upcoming plugin release.

    Thread Starter sanderrrrr

    (@sanderrrrr)

    Unfortunately both those entries are autoloaded, see the screenshot below:
    https://snipboard.io/3x9hDn.jpg

    So perhaps this is an error from an old version of the plugin?
    This screenshit is live and autoload is clearly on.
    Shall I disable it and turn it off?
    —-
    channel_statistics and cron_projects are the two largest entries in the entire options table! This seems extremely undesirable for a relative passive plugin that has no clear need for autoload.

    Hi,

    On what version of our plugin are you? I suspect it is not the latest.
    Yes you can turn the autoload off if you like.

    See:
    https://www.dropbox.com/s/oaqqsqnczmuazcj/Autoload-no.png?dl=0

    Thread Starter sanderrrrr

    (@sanderrrrr)

    Currently on version 11.6.3, have been using this for years so maybe this is some old code lingering around.
    i have set autoload to no for now; and would like it if the other (cron_projects) could also turn to no

    Thread Starter sanderrrrr

    (@sanderrrrr)

    Hello again,

    i noticed on a different website we manage the channel_statics is also on autoload = yes. It seems this isue is more widespread and might be affecting many websites.
    I have no set it to autoload = no. Is this OK to do?

    Hello there,

    Same issue here. Is this really mandatory to autoload “cron_projects” ? It’s my second biggest wp_options autoload after theme. (149kb)

    • This reply was modified 2 years, 6 months ago by tonuz.

    We just pushed out a new release of the plugin that no longer autoloads the cron_projects.

Viewing 10 replies - 1 through 10 (of 10 total)
  • The topic ‘channel_statics on autoload’ is closed to new replies.