fastcgi memory cache

  • Resolved hsntgm

    (@hsntgm)


    3 years, 5 months ago

    Hello,

    We use fastcgi server side caching. We set fastcgi cache path as /var/run so basically this is memory cache setup. All the assests loading from ram cache but the problem is minified/preloaded files by fvm use disk cache.

    Thanks.

Viewing 1 replies (of 1 total)
  • Plugin Author Raul P.

    (@alignak)

    Hi,

    Fastcgi cache is for page cache, so the location doesn’t need to be public as long as nginx is aware if it.

    Static files, such as the ones generated by FVM need to be publicly accessible over the internet, so it’s not the same thing. How would you deliver the files from /var/run if that directory is not publicly available (and should not be)?

    If your disk is slow, you can always create a tmpfs partition and mount it on the wp-content/cache directory.

    If you are on ubuntu, instead of /var/run you likely would want to use /dev/shm instead, to keep the /var/run directory free for your unix sockets (such as mysql for example).

    Ex:
    https://wp-rocket.me/blog/mount-folder-ram/
    https://docs.oracle.com/cd/E18752_01/html/817-5093/fscreate-99040.html

Viewing 1 replies (of 1 total)
  • The topic ‘fastcgi memory cache’ is closed to new replies.