• Resolved Ironos

    (@irongenetics96)


    I’m currently trying to figure out the preloader feature and would like to confirm the best practice for my setup:

    • Cache lifespan / cache-control max-age: 86400 seconds (1 day), because I use the AAWP plugin (Amazon affiliate) which requires daily cache purges to show updated prices.
    • Total URLs: ~700 (posts, pages, categories).
    • Preloader: enabled via cron once per day at 4:00 AM. swcfpc-preloader=1&swcfpc-sec-key= or should i just leave cache lifespan / cache control max age at default and use swcfpc-purge-all=1 con?
    • Config: I set define('SWCFPC_PRELOADER_MAX_POST_NUMBER', 750); so the preloader can cover all URLs in the sitemap instead of the default 50 in wp config

    My questions:

    1. Is preloading all ~700 URLs once per day (after purge) the recommended setup for SEO/performance?
    2. Or would you suggest leaving the default 50 and relying on normal traffic to warm the cache?
    3. Are there any downsides (server load, database growth, Cloudflare cache behavior) when running a full preload every day with this configuration? I see Scheduled actions are growing fast. with daily preload it can be 22.500! entries in a month

    Thank you for your advice

    • This topic was modified 9 months, 1 week ago by Ironos.
    • This topic was modified 9 months, 1 week ago by Ironos.
Viewing 1 replies (of 1 total)
  • Plugin Support rodicaelena

    (@rodicaelena)

    Hi @irongenetics96,

    Thanks for your question. A daily preload of all 700 URLs is generally not the recommended strategy. It can cause unnecessary server load and database bloat due to the large number of scheduled actions.

    A better approach is to use a hybrid strategy:

    1. Revert to the Default: Stick to a smaller daily preload number (e.g., 50 or 100). This will keep your most important pages warm.
    2. Rely on Normal Traffic: Let the rest of your URLs be cached naturally as visitors browse your site. The plugin is designed to handle this efficiently.

    This strategy will give you the benefits of a warm cache without overtaxing your server and database.

    Hope this helps!

Viewing 1 replies (of 1 total)

The topic ‘Recommended Preload Strategy’ is closed to new replies.