ShadowXVII edited a comment on issue #1685: Pagespeed causes high FTTB on nginx URL: https://github.com/apache/incubator-pagespeed-ngx/issues/1685#issuecomment-612871452 Sorry, I know it's a very vague question! I'll try and get some more metrics. The pagespeed is on a disk, with a redis cache also. The proxy type is Azure Front Door which is Microsoft's CDN network. I have unique query URLs cached -- it should also respect cache headers from source. Maybe the two aren't interacting well together. Switching pagespeed off and on using the URL parameters causes a difference:  The timings when debug is enabled are as follows: ```<!-- mod_pagespeed on Filters: db Debug hw Flushes html Options: AvoidRenamingIntrospectiveJavascript (aris) True EnableCachePurge (euci) True EnableRewriting (e) 1 FileCacheCleanIntervalMs (afcci) 86400000 FileCacheInodeLimit (afcl) 500000 FileCacheSizeKb (afc) 2048000 RewriteLevel (l) Pass Through Statistics (ase) True StatisticsLogging (asle) True #NumFlushes 0 #EndDocument after 216021us #Total Parse duration 2208us #Total Render duration 695us #Total Idle duration 213813us The following filters were disabled for this request: SupportNoscript -->``` The config is currently as follows ```# pagespeed pagespeed standby; pagespeed FileCachePath "/var/cache/pagespeed/"; pagespeed FileCacheSizeKb 2048000; pagespeed FileCacheCleanIntervalMs 86400000; pagespeed FileCacheInodeLimit 500000; pagespeed RedisServer "localhost:6379"; pagespeed RewriteLevel PassThrough; pagespeed DisableFilters "rewrite_images,resize_images"; pagespeed Statistics on; pagespeed StatisticsLogging on; pagespeed LogDir /var/log/pagespeed; pagespeed AdminPath /pagespeed_admin; pagespeed EnableCachePurge on; pagespeed PurgeMethod PURGE;``` So if I interpret those stats correctly, the long Idle duration suggests the FTTB is mostly caused by the underlying page?
---------------------------------------------------------------- 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
