• Resolved klooperator

    (@klooperator)


    Hi,

    I am having a trouble automatically caching pages.
    I have action based, disk cache with rewrites enabled, CF autopurge is on, and warmup table has disabled preloading.
    Also have more then 10000 posts on site.
    The site runs on custom VPS ( 4 cores) and doesn’t have CPU problems.

    So, pages dont cache automatically. I can cache them manually though.
    In logs I get this message:
    March 24, 2019 12:37 pm [Event] Thread for https://www.mydomain.com/ is not available ( Memory:3.05Mb CPU:1.51% )

    Any suggestions?

Viewing 4 replies - 1 through 4 (of 4 total)
  • Plugin Contributor Fred

    (@fredawd)

    Hi,

    You will notice those warnings because Swift will log if someone load the page, but prebuild only is enabled in Settings->Optimization->General. Did you enable Prebuild Cache Automatically?

    These articles might worth reading regarding warmup table.
    https://swteplugins.com/docs/warmup-table/
    https://swiftperformance.io/kb/prebuild-cache-is-not-working/

    Thread Starter klooperator

    (@klooperator)

    When I do it this way, I do get some pages cached, but it goes on order of a warmup table. I want to cache pages that are currently looked at.
    In your docs I read that for that you need to disable automatic cache prebuild and then it will cache only after someone visits some post.

    When I try with automatic cache prebuild I got like 3 cached pages, and then same error in logs.
    Maybe there is some php module or server conf this plugin is relying on?

    Plugin Contributor Fred

    (@fredawd)

    If you want Swift cache pages on first visit, then you should disable Prebuild Cache Automatically and enable Optimize in Background

    Swift use WordPress Cron Events. If default WP Cron is disabled, Swift will load wp-cron.php in every minute while the plugin admin dashboard is opened.

    Plugin Contributor Fred

    (@fredawd)

    Since this topic has been inactive for a while, I’m going to go ahead and mark as resolved. Don’t hesitate to reopen or create a new topic if you still need help!
    Thanks for understanding!.

Viewing 4 replies - 1 through 4 (of 4 total)
  • The topic ‘Thread not available’ is closed to new replies.