You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'd love to have a way to get some cache statistics out of wp-cli. Things I'm thinking of would be like
page cache hit rate
cache avg response time
cache eviction rate
% of cache used
% of cached items access over x number of minutes (I don't know any tool that does this currently....would be great data for sizing a memcached server. Could have this run for 10 minutes at the command line and collect data, then offer a report at the end. Will be tricky)
number of database queries saved by using caching
With the various object cache and advanced cache files out there this might be difficult to implement universally. Maybe it could be done for the most common caching plugins, or maybe we could build a framework that caching plugins can tie into with some simple integration code. Or this might be nearly impossible, but it'd be cool if we could do it.
The text was updated successfully, but these errors were encountered:
Mostly I'm thinking of the use case of memcached, but it could be applicable to other cache backends too. Some of these stats can be pulled directly from Memcached and some would need to be monitored over time. Not thinking of it specifically for web PHP processes, but more from an overall cache health perspective. wp-cli/profile-command#128 is a great idea and along the lines of what I was thinking.
I'd love to have a way to get some cache statistics out of wp-cli. Things I'm thinking of would be like
With the various object cache and advanced cache files out there this might be difficult to implement universally. Maybe it could be done for the most common caching plugins, or maybe we could build a framework that caching plugins can tie into with some simple integration code. Or this might be nearly impossible, but it'd be cool if we could do it.
The text was updated successfully, but these errors were encountered: