Regular caching vs preloading

  • swahlgren

    (@swahlgren)


    8 years ago

    I run a website on a shared hosting platform and I’m thus interested in minimizing the resource impact of using WP Super Cache while still getting the majority of benefits from caching.

    Preloading is obviously a great feature but it also seems like it uses a lot of resources. I have thousands of posts so a preload of the entire website takes hours where the CPU looks to be quite high and I’d thus like to keep preloading to a minimum. Is it possible to do a full preload of all files and then afterwards schedule preloading the 20 newest once every 24 hours?

    Regarding the preload cache versus the regular cache system it says in the settings that preloaded files won’t be deleted with garbage collection. Does this mean preloaded files are never updated?

    PS: Other suggestions regarding minimizing resource usage are greatly appreciated 🙂

    https://wordpress.org/plugins/wp-super-cache/

Viewing 1 replies (of 1 total)
  • massimod

    (@massimod)

    8 years ago

    Hello.

    If you are short on resources on shared hosting, preload will not help you. Because you will have a huge ammount of inodes (files, the static cached html pages). And if you have a lot of posts (as you say), maybe you will run out of inodes.

    Best thing for you is to use Hyper Cache, since it is the best for Shared Hosting. Extremely light on load and resources.

    Still, there are some great shared hosting companies, maybe you should also look for them.

Viewing 1 replies (of 1 total)
  • The topic ‘Regular caching vs preloading’ is closed to new replies.