andrewbrg commented on issue #1686:
URL:
https://github.com/apache/incubator-pagespeed-ngx/issues/1686#issuecomment-622948077
Ok, so I have an interesting update @Lofesa .
I pushed the new setup to production and got 404s on pagespeed images
immediatly.
Let me explain the setup of the pagespeed nginx servers.
There are two of them and each is running as a docker container. Each
pagespeed instance is set to write its file cache to a mounted hard drive
(there are 2 separate hard drives) one per pagespeed server.
The data on this hard drive persists across re-deployments of the pagespeed
nginx servers, which happens every time the codebase is deployed.
It got me thinking, to see 404s on a new empty memcached DB means that the
DB being full has nothing to do with it, but it is likely tied to the local
file metatdata cahe or whatever.
What am i doing wrong? Should I not persist this data and let it expire on
each deployment? This is the file cache:
pagespeed FileCachePath "/var/www/pc/pagespeed/";
pagespeed FileCacheSizeKb 728000;
pagespeed FileCacheInodeLimit 5000000;
pagespeed FileCacheCleanIntervalMs 36000;
/pc is the root of the mounted persistent drive.
There is also this:
pagespeed LRUCacheKbPerProcess 8192;
pagespeed LRUCacheByteLimit 16384;
Should i get rid of this file cache? Is it possible to set up pagespeed so
that 100% (everything) is in memcached or redis?
Thanks
Andrew
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
