Inquiry About Cache Pollution in gcache LRU Implementation

[Toastqueen]

I am reaching out to inquire about the potential for cache pollution in this LRU implementation. In scenarios where the cache handles a mix of frequently and infrequently accessed data, such as in a Cache-Aside pattern for API responses, I am concerned about the risk of low-frequency data displacing high-frequency data, which could reduce cache efficiency.

Could you clarify whether the LRU implementation includes any mechanisms to mitigate cache pollution, such as partitioning, active/inactive lists, or visit-frequency tracking (similar to ARC or Linux page cache)? If not, would switching to the ARC eviction policy provided by the library help address this issue?