You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@pagespeed.apache.org by GitBox <gi...@apache.org> on 2021/04/11 20:28:48 UTC

[GitHub] [incubator-pagespeed-ngx] jmarantz commented on issue #1679: pagespeed with load balancer (nginx) and front-end (apache)

jmarantz commented on issue #1679:
URL: https://github.com/apache/incubator-pagespeed-ngx/issues/1679#issuecomment-817367780


   From a functionality perspective, it is fine to have PageSpeed running on
   multiple servers with isolated caches. You will wind up storing each
   resource and re-optimizing each image on every server and storing it in
   every cache. This is because all the information needed to reconstruct each
   optimized asset is encoded in the rewritten URL.
   
   The advantage of sharing a cache via memcached or Redis is that an image
   optimized on pagespeed server A can then be served from a request landing
   on pagespeed server B.
   
   
   On Sun, Apr 11, 2021 at 5:04 AM Lofesa ***@***.***> wrote:
   
   > Yes. Any pagespeed installation with more than 1 server, for better
   > performance, need a shared cache.
   > You may implement a sigle cache for each server, file based, but this
   > increases resouce use and perhaps you need to grant some affinity for user
   > request (all request from a user go to the same backend server).
   >
   > —
   > 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#issuecomment-817274563>,
   > or unsubscribe
   > <https://github.com/notifications/unsubscribe-auth/AAO2IPNCHSAQ2VZCEYD7QILTIFQ27ANCNFSM4KQ4JUGA>
   > .
   >
   


-- 
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:
users@infra.apache.org