-
Notifications
You must be signed in to change notification settings - Fork 121
Tutorial for preload cache? #416
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
Hi @alexlii1971, Enabling preload cache for Nginx FastCGI Cache is quite straightforward! You just need to check the "Preload Cache" option in the Nginx Helper plugin settings. Here's how to do it:
The preload functionality works out of the box with the standard Nginx FastCGI Cache setup, so no additional Nginx configuration is needed. |
Hi @Vedant-Gandhi, Thanks so much for your reply. To better manage memory and CPU usage, it would be great if you could clarify how it works,since I just note there are a lots of Memory usage on server, and lots of queries internally after enable preload. I am not sure if it is relevant to preload cache on Nginx helper. Anyway, it would be much helpful for us do anything forehand. Thanks |
Hi @alexlii1971, Looks like you're seeing a spike in queries after enabling preload for the first time. This is completely normal! The preload process sends a batch of requests only during initial activation, which temporarily increases memory usage and query count. Once preload completes, these numbers will return to normal levels. This is a one-time event that happens when the feature is first activated. |
Hello,
Any configuration needed to enabled preload cache for nginx fastcgi cache?
Thanks
The text was updated successfully, but these errors were encountered: