Cache lookups expired.

[Jonathan Garbee]

After upping my cache to a whopping 14GB for image storage the cache misses came down to 1% current. Which is *much* more acceptable than 73%. However now the cache lookups expired is sitting at 48.26%. Only cache lookups expires and cache misses have any percent showing on the console currently.

Could this be something that others going through the configuration process could see?

I am upgrading the mod now to the latest available which will upgrade the console. I'll also enable the load from file option to see if that helps since I notice that in the documentation and my expires (via apache) for images is a month.

[Shawn Ligocki]

Great to hear that your cache miss rate has effectively gone away. LoadFromFile should help a lot for high expiration rate. I'm surprised that you're getting a 48% expiration rate when you have 1 month cache headers! Is that only for images, or for JS and CSS too? If it's not for JS and CSS, they might be the ones expiring...

[Jonathan Garbee]

Yea, I read through the LoadFromFile configuration stuff and it turns out that should only be used for static files. In my case images are being dynamically generated into the proper size from the master image. So, doing LoadFromFile isn't recommended and/or feasible due to that. And since the cache headers are a month and the recommendation is to up that (as we both know one month should be plenty to avoid this) I doubt increasing it more will help.

Also after this update I seem to now not be getting webp images out. So, I am going to do some tweaking to the config of both pagespeed and the backend tonight. Then I'll chill for a bit to collect data and see if things improve and report back at some point next week with more information. 

I have updated to the latest release about 3 hours ago. I am now with 8.43% cache misses, 3.61% on cache lookups expiring, and for the first time 2.35% failing from the domain not being authorized. This last one (authorization of domain) could be something I just did messing around, so I wouldn't put much weight in that one until I reconfigure things in detail tonight.

[Jonathan Garbee]

I realized something that is perhaps pretty major... Is this console showing errors from across all domains pagespeed is touching if the virtualhost configuration is not in use?

I am now believing it is since I am seeing these errors even though on the domain I'm accessing it from is clearly fixed up properly. There are a few other development sites on this host that I work on regularly and they aren't configured for performance, however I also failed to get virtualhost configuration with pagespeed working. So I'm thinking these errors are from the other domains now since there is nothing in my log for the primary site.

[Shawn Ligocki]

It depends whether or not you have UsePerVhostStatistics enabled. Enable it and then your console should only reflect the single Vhost.