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
Right now we just track get/set and a couple of other things. It would be better if the Stats hook were modified into tracking all CRUD groups (at least).
Perhaps it would be nice to track the count of results in some form. We could keep track of results on a per-action basis (this is just noted for my memory).
Maybe then we could support stats retrieval on a per-command basis which allows us to provide additional info about that stat.
Cachex.stats(:my_cache)# very high level stats (op count, etc)Cachex.stats(:my_cache,:get)# include things like hit rate using info in the `:get` keyCachex.stats(:my_cache,[:get,:set])# same as above but for both actionsCachex.stats(:my_cache,:raw)# everything we have collected (the struct above)
The text was updated successfully, but these errors were encountered:
Been thinking on this more and I like the above. Although I think there should also be a :global entry which is very general statistics (similar to those tracked currently). Easy to get a high-level overview of your cache usage that way.
If we default to using :global, it has the benefit of keeping the API compatible for anyone relying on the current formats.
Right now we just track get/set and a couple of other things. It would be better if the Stats hook were modified into tracking all CRUD groups (at least).
Perhaps it would be nice to track the count of results in some form. We could keep track of results on a per-action basis (this is just noted for my memory).
Maybe then we could support stats retrieval on a per-command basis which allows us to provide additional info about that stat.
The text was updated successfully, but these errors were encountered: