jmarantz commented on issue #1686:
URL:
https://github.com/apache/incubator-pagespeed-ngx/issues/1686#issuecomment-623114086
Hi -- I want to clarify some confusion on this thread.
When you have multiple servers running mod_pagespeed, they do *not* need to
share a cache(*). Thinking about this another way, caches generally may
evict assets at any time, and the system needs to work correctly. So the
URL generated by mod_pagespeed has all the information that is needed to
reconstruct the optimized asset from the original one.
If 404s are being served, it is *not *because the caches are separate. It
is most likely because of a bug, or because one of the instances is unable
to fetch the origin resource for some reason.
It *is* beneficial to use a shared cache setup like memcached or redis,
because it improves performance (response time, and likelihood of getting
an optimized asset).
* exceptions to the above:
1. the outline_javascript and outline_styles filters depend on caches
not evicting. We don't recommend their use :)
2. If you use LoadFromFile then you definitely need access to the
file-system where the assets are from each resource.
More detail on how caching works in mod_pagespeed:
http://modpagespeed.jmarantz.com/2012/12/caching-in-modpagespeed.html
Hope this helps,
-Josh
On Sun, May 3, 2020 at 7:58 AM Andrew Borg <notificati...@github.com> wrote:
> Thanks @Lofesa <https://github.com/Lofesa>
>
> From that thread what i took away was to set:
>
> —
> 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/1686#issuecomment-623098797>,
> or unsubscribe
>
<https://github.com/notifications/unsubscribe-auth/AAO2IPK4I3B4UFISG7REJH3RPVL6NANCNFSM4MTB4TGA>
> .
>
----------------------------------------------------------------
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
