• Resolved Vladi

    (@pbvlad)


    Hi!

    I was checking some of the slow queries on our site and noticed that the wp_options table was showing as a slow query. Upon further investigation, I noticed that the autoptimize_ccss_queue field (autoload = yes) had grown to over 50MB in size!

    Uninstalling the CCSS plugin removed this field, but since reactivating the plugin, the field is again growing in size quite rapidly. Oddly, all of the pages in the queue should be covered with the AUTO rules for the various conditional tags, but somehow it just gets bigger by the hour.

    I would appreciate your assistance in getting this figured out. Thank you!

    P.S. I have enabled debug mode for now.

    • This topic was modified 5 years, 6 months ago by Vladi.
Viewing 5 replies - 1 through 5 (of 5 total)
  • Plugin Author Optimizing Matters

    (@optimizingmatters)

    * so you have AUTO rules, correct?
    * autoptimize_ccss_queue gets normally gets pruned by the cronned ao_ccss_maintenance action (removing jobs older then 24h if more then 100 jobs are in the queue), maybe check with wp crontrol if that is running?
    * might “aggregate inline CSS” be on and if so can you disable that to see if that allows the existing rules to be used iso new jobs being created?

    frank

    Thread Starter Vladi

    (@pbvlad)

    Hi Frank, thanks for your prompt response!

    * Yes, I do indeed have AUTO rules in place for is_front_page, is_single, is_archive, etc.
    * I am sure that ao_ccss_maintenance is not running right, as the queue is absolutely massive and not pruned. Checking with WP Crontrol now!
    * I will try to disable the option and circle back!

    • This reply was modified 5 years, 6 months ago by Vladi.
    Thread Starter Vladi

    (@pbvlad)

    I ran the maintenance cron manually after turning off the aggregate inline option and the queue is still showing hundreds (thousands?) of unprocessed, new jobs from a day ago. I’ll try to deactivate the plugin and turn it back on.

    A lot of the jobs involve the is_attachment target rule, is there a way to omit those targets entirely, as we don’t have separate attachment pages that users can view anyway. Thank you!

    Plugin Author Optimizing Matters

    (@optimizingmatters)

    I ran the maintenance cron manually after turning off the aggregate inline option and the queue is still showing hundreds (thousands?) of unprocessed, new jobs from a day ago. I’ll try to deactivate the plugin and turn it back on.

    the maintenance job only removes jobs that are 24h old or more, guess that’s what’s going wrong here ..

    A lot of the jobs involve the is_attachment target rule, is there a way to omit those targets entirely, as we don’t have separate attachment pages that users can view anyway

    yes; create a manual rule for is_attachment and either add critical CSS for that yourself or set it to none to avoid new AUTO rules being created.

    Thread Starter Vladi

    (@pbvlad)

    Great, I set the is_attachment conditional to none and will keep an eye on the queue going forward. Thank you!

Viewing 5 replies - 1 through 5 (of 5 total)
  • The topic ‘CCSS Job Queue grows and grows and…’ is closed to new replies.