Preload after finish overwrite

  • jonalange

    (@jonalange)


    3 months ago

    So, I was wondering how this feature actually works.

    We have a page with a lot of custom posttypes and attachments on a single page.
    This is how the preload page ?action=wpfastestcache&type=preload looks like:

    homepage: 1/1
    customposttypes: 0/2068
    post: 0/0
    attachment: 372/2258
    page: 28/28
    category: 0/1
    tag: 0/1
    customTaxonomies: 0/1271

    The page is extremely slow without cache and takes very long to load. With a full cache, it’s just some ms until it’s loaded.

    Our server is dedicated and quite powerful, but the plugin limits us to 12 pages to be cached per minute. I have set up a cronjob the the URL, to keep the cache constantly running.

    1. Is there any way to cache more than 12 pages per minute?
    2. I have checked the option Restart After Complete to have newer posts appear once the cache is done and starts over.
    How does the restart work? Does it clear all the cache when it’s finished and purge it, so until it’s cached again the page will be super slow again? Or will it start at 1, clear it, cache it again and go to the next?
    So will it overwrite them one by one and update the cache? Or will it be remove completely and started fresh?


    If it’s removed completely, that’s not really and option for us, because then 50% of the time the page is super slow. What would be a better option for us then? I want to have the page cached, but also update the cache automatically from time to time to get newer post in the cache.

    Any suggestions?

Viewing 4 replies - 1 through 4 (of 4 total)
  • Thread Starter jonalange

    (@jonalange)

    Actually just after posting if found this option in the docs:

    4. What is the “Number” Option Used? For?

    It depends on the power of the server. If you have a ordinary?hosting?package, you should not set more than?4-6. But if you have a?VPS, you can set?10-12. You can set the preload number to a maximum of 12 under the Preload settings.

    If you want to set the number 12 or more, you need to add the following lines after?<?php?which exists at the top of?wp-config.php?file. However, we do not recommend to increase the number more than 12 unless you have a powerful dedicated server.

    define('WPFC_PRELOAD_NUMBER', 15);

    How to determine if the server can handle the load? 15 isn’t actually that big of an improvement over 12. I was more thinking about 50 or something like that.
    Is there any benchmark to build on? Let’s say I can increase the number of pages until it takes X seconds until it’s finished or something like that?

    Plugin Author Emre Vona

    (@emrevona)

    If the cronjob runs every minute, you do not need to set the number greater than 12. No need to strain the server.

    Thread Starter jonalange

    (@jonalange)

    @emrevona Thanks, but what about the reset after restart? This is the most important part for me here.

    Because if the cache is completely cleared after it‘s done, it will be slow again.

    And 12 items per minute, is 720 per hour. Alone for the current setup it will take about 7 hours until the cache is built once.

    Plugin Author Emre Vona

    (@emrevona)

    The entire cache is overwritten instead of being cleared.

Viewing 4 replies - 1 through 4 (of 4 total)
  • You must be logged in to reply to this topic.