Lofesa commented on issue #1686: URL: https://github.com/apache/incubator-pagespeed-ngx/issues/1686#issuecomment-623001078
In parts, as Jack the ripper would say =:-)) Yes, I think redis is better that memcached for the pagespeed purposes. They have no object size limit and can be scaled configuring a cluster. The info you get from the +debug is not relevant to the issue. You have enabled the inline image filter and have a max size the image can have to be inlined (if tou don´t have this max size, this parameter have a default value) The fact that you have set 2 different file-cache is the most relevant info. When you have 2 servers spreading the same files, you need that the cache are the SAME for bath servers. This can be achieved by 2 ways: 1.- A shared file system. This is advised againts it, shared filesystems add to much latency 2.- A shared database, like memcached or redis. Yuou need to configure pagespeed FileCachePath in both servers, but you need to be sure nothing is writen in thses paths. And again, if a object does not fit in the memcache db, then this object is written to the disk. What could be happening here? Well, say you make a request to the server A, this make all the html come from server A to the client, but before this, pagespeed does it magic and rewrite the resources in the server A pagespeed cache When the client have the html, it does request for the resources, if these resources are in server A pagespeed cache and the request go to that server all is ok, but if the request goes to server B it know nothing about this rewrited resource. ---------------------------------------------------------------- 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
