Two sets of data provide complementary information, cache activity and file request profile. Activity information summarizes the cache search behaviour, in particular that of the hash table. Requests involving scripts, and some others, never attempt a cache search. This is very efficient. This is decisive and is also very efficient.
Collisions require further processing and are far less efficient.
A large number of cache misses compared to searches may only indicate a large number of non-cacheable requests and so depending on that further datum is not of great concern. Files information summarizes the site's file request profile. If this percentage is high it means most files loaded are never hit, indicating the site's request profile is possibly unsuitable for caching. Other considerations also apply when assessing the benefit of having a cache. The explanation for this would be one or two frequently requested files being hit while most others are loaded, never hit, and flushed as other files request cache space.