Hey Erick,
So I am investigating the point where we can limit the values that are
cached using {!cache=false} (we already use it in some of our cases)
So in general there is 0 evictions on filter cache side but whenever we hit
this max limit there is a spike in evictions as well (which is expected
Well, when you hit the max capacity, cache entries get aged out and are
eligible for GC, so GC
activity increases. But for aging out filterCache entries to be noticeable, you
have to be
flushing a _lot_ of them out. Which, offhand, makes me wonder if you’re using
the filterCache
appropriately.
