Preloading is consuming too much CPU

  • Resolved kozbisov

    (@kozbisov)


    2 years, 8 months ago

    Hello,

    As the title says, preloading cache is consuming too much CPU. My hosting service is not quite good and I have 1GB ram and CPU has 1 thread. When I try to preload my cache. I have too much posts in the website, it’s a news site. So, CPU usage goes up to almost 100% every time and I’m getting errors on the website in the meanwhile. Is there any way to increase interval for crawling URLs to be preloaded? Please help me with that.

Viewing 13 replies - 1 through 13 (of 13 total)

  • I have a similar problem. WPO preload process generates a lot of queries. My hosting plan only allows a maximum of 150,000 queries an hour. Once reached, the site crashes. It would be prevented by pacing the preload process into hourly intervals, a small chunk at a time, so it does not overwhelm the server. Please consider. It will help many users.

    @francoc30 @kozbisov try the plugin Flying Pages.

    Hi @laserstore.
    Thanks for your suggestion. I’ll take a look.
    I will use test wpo together with Flying Pages. Would there be any problems? I guess I should not run preload in wpo, right? I do have minify enabled in wpo. Should that be turned off or keep it on?

    @kozbisov I’ll check this with our development team and update you soon.

    Thank you for your time and patience.

    @francoc30 disable wpo preload and let flying pages do the work. In it you can configure the range while this option does not exist in wpo.

    • This reply was modified 2 years, 8 months ago by laserstore.

    @francoc30 Have you tried the suggestion by @laserstore does it helps to fix the issue?

    Thread Starter kozbisov

    (@kozbisov)

    I tried that and it’s working better than your preloading function. Thanks @laserstore

    I tried that in my dev site. It did not improve with page loading speed with my current settings in wpo (no preloaded cache, minify enabled). As I understand from Flying Pages documentation, FAQ and Support forum, the plugin is more like a browser cache. So there is no heavy loads or queries on the server. It also depends on cached pages.

    With wpo preloaded cache, my non-login pages load on average under 2 secs which I am happy with. My issue of wpo generates a lot of queries while doing preloading remains. Preloading is good, but just need to pace it out so that it does not crash sites. Please look at this and many users will be happier. Thanks.

    @francoc30 Okay we are looking into this and a fix will be released in the next version.

    Thread Starter kozbisov

    (@kozbisov)

    Thanks for your interest! I’m looking forward for the next update.

    Thanks. I am looking forward to the new feature.

    Such improvement will likely allow me to use the Preload Scheduler. Currently I have to manually manage the preloading to avoid going over my plan’s query limit.

    One other thing that prevent me to use the scheduler is the appearance of the pop up message “Unexpected Response received”. I have to click ok to dismiss the pop up so that the preload process can continue. With the scheduler, no one is going to attend to any pop up message. Then preload would not proceed. Hope this issue can be resolved as well.

    @francoc30 Okay I’ll share this information as well to our development team.

    Thanks Harshad.
    WPO is really good in improving load speed. Love it. Hope it will continue to address issues to better the plugin. Great work.

Viewing 13 replies - 1 through 13 (of 13 total)
  • The topic ‘Preloading is consuming too much CPU’ is closed to new replies.