uhlhosting edited a comment on issue #1720:
URL: 
https://github.com/apache/incubator-pagespeed-ngx/issues/1720#issuecomment-738669538


   1. Added the changes in pagespeed.conf
   
   2. So I should either inline or outline js / css. What is best in your 
experience?
   
   3. These I tought to leave them by default were in a wp config for 
pagespeeed . Might be irelevant now, since the config might be old.
   
   4. replaced the 3 lines with 1 suggested.
   
   5. changed to true
   
   6. trippled the sizes here
   
   7. I have reenabled the filter to see if any improvements.
   
   8. Disabled the downstream
   
   Will need to look a bit more into inline best practices.
   
   evicted_keys:0 sits on zero now. While the redis memory is not limited.
   
   Also can you explain me a bit the role of ?$ps_dollar in 
   location ~ "^/ngx_pagespeed_beacon$ps_dollar" { }
   
   I have seen also variant without ps_dollar after $ .
   
   How can I avoid these:
   ```
   [Fri, 04 Dec 2020 09:21:17 GMT] [Info] [1794288] Inside CSS: 
https://uhl.site/wp-content/uploads/oxygen/css/universal.css?cache=1606492394&ver=5.5.3:
 Image MIME type could not be discovered from reading magic bytes; rewriting 
dropped.
   
   [Fri, 04 Dec 2020 09:20:13 GMT] [Info] [1794288] https://uhl.site/:32: 
https://uhl.site/wp-content/uploads/2020/11/cropped-web-programming-32x32.png: 
Too busy to rewrite image. How can I make sure pagespeed is never too busy? I 
run on a Xeon @4 GHZ with 8 CPUs assigned, 10 GB ram on this test machine and 
all runs on pure NVMs.
   
   [Fri, 04 Dec 2020 09:21:17 GMT] [Info] [1794286] Unable to insert object of 
size: 72045, cache limit is: 71232 --> a bit confused on where this value is 
set.
   ```
   
   `[Fri, 04 Dec 2020 09:19:03 GMT] [Info] [1794286] Initializing shared memory 
for path: <unplugged>. -- Is this normal?`
   


----------------------------------------------------------------
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


Reply via email to