jmarantz commented on issue #1679: pagespeed with load balancer (nginx) and front-end (apache) URL: https://github.com/apache/incubator-pagespeed-ngx/issues/1679#issuecomment-583859940 I lost track of the recommendation about caches and where that came from. If you have any image or CSS optimizations, or URL-rewrirting enabled, you must have caches in mod_pagespeed to store optimized results. mod_pagespeed is designed to serve unoptimized resources initially while running optimizations in the background. The cache is where those are stored. When LoadFromFile is used, mod_pagespeed does not need to store and cache resources from the origin, but it does need to store the optimized results. Even if you don't have optimizations enabled that require a cache, I doubt mod_pagespeed would start up without one; we never tested that to my recollection. The ideal configuration is to use the shared-memory cache as an L1, and memcached/redis as an L2. With memcached you need a file-cache fallback. And you always need a file-cache path, which is where the cache-purge information is stored so it persists across restarts. If for some reason, shared-memory cache cannot be used, you can use an in-memory LRU as an L1, and there will be separate caches across child apache/nginx processes. All of these can be used in multi-server environments. Hope this helps, -Josh On Sat, Feb 8, 2020 at 6:46 PM Lofesa <notificati...@github.com> wrote: > @salvoaranzulla <https://github.com/salvoaranzulla> Maybe you can use it, > as far as the LRUcache is a cache not shared even between the server > processes. If you have configured nginx to run, say, 4 processes the you > have 4 LRUcache. > SharedMemory stores metadata about the optimized resurces, if you > configure it in each server, one server don´t know what metadata has > created an other server. > If you store it in a centraliced repository, aka external cache, these > metadata can be shared too. > > — > You are receiving this because you were mentioned. > Reply to this email directly, view it on GitHub > <https://github.com/apache/incubator-pagespeed-ngx/issues/1679?email_source=notifications&email_token=AAO2IPI4P5CVFJ2USZ3AUO3RB473RA5CNFSM4KQ4JUGKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOELF6N6Q#issuecomment-583788282>, > or unsubscribe > <https://github.com/notifications/unsubscribe-auth/AAO2IPMTBQ4XIFSK3WX2IQLRB473RANCNFSM4KQ4JUGA> > . >
---------------------------------------------------------------- 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 With regards, Apache Git Services
