Garbage collector cron times

  • Resolved fidoboy

    (@fidoboy)


    1 year ago

    I’ve noticed long times on the cron docketcache_gc when executing from wp-cli. Is this normal? When calling

    wp cron event run --due-now

    I get this line:

    Executed the cron event 'docketcache_gc' in 114.673s.

    Also looking at the WP Crontrol manage page it displays that crons are not being executed, but my real cron task calling wp-cli is running. So it seems that for any reason, the garbage collector task is not being completed.

    • This topic was modified 1 year ago by fidoboy.
Viewing 2 replies - 1 through 2 (of 2 total)
  • Plugin Author Nawawi Jamili

    (@nawawijamili)

    Hi there,

    The garbage collector (GC) will scan cache files every 5 minutes. Sometimes, when the cache is too large to scan, GC will take a long time to complete and sometimes it will fail to complete.

    You may try to disable GC Cron and run it manually by using this command:

    wp cache run:gc

    Please refer to the docs here: https://docs.docketcache.com/constants#docket_cache_gcron_disabled

    And an additional CLI command here: https://docs.docketcache.com/wp-cli

    Thanks.

    Thread Starter fidoboy

    (@fidoboy)

    Many thanks for detailed information. I’ve uninstalled the plugin finally and change it by another one based on Redis.

    This issue should be advertised from the beginning to avoid many headaches. My cron is based on WP-CLI and runs every two minutes so having tasks very resource consuming like this one is a “no go”.

    The plugin looked very promising, but unfortunately it’s very slow. So the performance gain in one side is being lost in another one.

    It’s also a real pain to reload the settings page every time a single option is being changed.

    Keep up the work anyway. May be in the future this could be a good plugin to consider.

    Kind regards,

Viewing 2 replies - 1 through 2 (of 2 total)
  • The topic ‘Garbage collector cron times’ is closed to new replies.