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 2019/04/02 13:57:09 UTC

[GitHub] [incubator-pagespeed-ngx] dennisjac commented on issue #1639: Values on statistics page not updated

dennisjac commented on issue #1639: Values on statistics page not updated
URL: https://github.com/apache/incubator-pagespeed-ngx/issues/1639#issuecomment-479008203
 
 
   This is what my configuration looks like:
   ```
   Options
     AvoidRenamingIntrospectiveJavascript (aris)  True
     BeaconUrl (bu)                               /ngx_pagespeed_beacon
     EnableRewriting (e)                          1
     FileCacheCleanIntervalMs (afcci)             3600000
     FileCacheInodeLimit (afcl)                   500000
     FileCachePath (afcp)                         /var/cache/nginx/ngx_pagespeed_cache
     FileCacheSizeKb (afc)                        10485760
     LRUCacheByteLimit (alcb)                     32768
     LRUCacheKbPerProcess (alcp)                  16384
     RespectXForwardedProto (rxfp)                True
     RewriteLevel (l)                             Core Filters
     StatisticsPath (nsp)                         /ngx_pagespeed_statistics
   ```
   The documentation says that if no explicit shared-memory cache is specified there is a default one that will be used.
   What are the appropriate values for the cache sizes? The file cache directory is currently 7GB in size but the default shared-memory cache in only 50MB which seems tiny. On the other hand if I would increase this to say 5GB (the server has 16GB of RAM) then the snapshotting would probably cause massive disk i/o when all of this is written out.
   
   For some reason pagespeed is causing around 200 write IOPS for no apparent reason and my hope is that by configuring the in-memory caching correctly that I can fix this issue. It seems unlikely that pagespeed is updating so many files all the time so I suspect it might have something to do with metadata. 

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


With regards,
Apache Git Services