The number of times the cache object has been read on this cache server.
Hits are counted independently on each cache server and incoming requests may be handled by any cache server in a data center; therefore, consecutive requests for the same resource may encounter values of
obj.hits that are lower than previously encountered values.
Due to the effects of clustering, every cache object will have one server within the data center that serves as the primary storage location for that object, determined using a consistent hashing algorithm. However, particularly popular objects may also be temporarily cached on other cache servers within the same data center to avoid overloading the primary. When the object is found on the primary node, the value of
obj.hits is likely to be much higher than if the object is found in cache on a non-primary node.