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-582918258 That is an interesting idea, and I can see the potential value. But the system isn't quite designed for that use-case. The reason, I'm guessing, that you'd prefer this architecture to simplify using ngx_pagespeed in the proxy and removing it from the Apache instances, is that you want to keep the proxy lean, and have the Apache instances take care of all the hard work of (say) image optimization and URL fetching. The problem in practice is that when the standby ngx_pagespeed instance sees a .pagespeed. URL that is *not* in the cache, it will need to serve it; it won't proxy the request through to the backend servers. To serve it, it will need to fetch it and optimize it. Maybe if your cache TTLs are long and your memcached instance is large, that will rarely happen. But in that case you will do pretty well at steady-state with just ngx_pagespeed at the proxy. On Thu, Feb 6, 2020 at 7:48 AM salvoaranzulla <notificati...@github.com> wrote: > Hi, > > We have a lod balancer with nginx (proxy_pass) and many front-end with > apache and mod_pagespeed. We use memcached servers for mod_pagespeed cache. > > I'd like to know if it's a good idea installing ngx_pagespeed on load > balancer and configuring it with: > > pagespeed standby; > pagespeed MemcachedServers "same memcached server of mod_pagespeed of > frontend"; > > to avoid request to Apache (and mod_pagespeed) from nginx load balancer > for already optimized resources (*.pagespeed.* file). > > Thanks, > Salvatore > > — > You are receiving this because you are subscribed to this thread. > Reply to this email directly, view it on GitHub > <https://github.com/apache/incubator-pagespeed-ngx/issues/1679?email_source=notifications&email_token=AAO2IPLXRJDDGGLFKNDQVMLRBQBKTA5CNFSM4KQ4JUGKYY3PNVWWK3TUL52HS4DFUVEXG43VMWVGG33NNVSW45C7NFSM4ILQBRKA>, > or unsubscribe > <https://github.com/notifications/unsubscribe-auth/AAO2IPPNREICSOCAWVSJDX3RBQBKTANCNFSM4KQ4JUGA> > . >
---------------------------------------------------------------- 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
