garbage collection "unbearable" for millions of entries with different entry sizes about ccache HOT 3 OPEN

otherwise, any suggestion on how I can reduce load of gc by changing my code (which i think is not the problem) but maybe changing your code manually?

from ccache.

i'm using mostly the layeredcache feature / function

from ccache.

Hmmm.. Thanks. I'll have to take a look and think more about it. Off the top of my head though, the default itemsToPrune is 500, so a smaller value would obviously result in a faster gc, but at the cost of the gc being called more often.

As for the memory overhead..I did look at that before. I can look again, but I think what I concluded last time is that this is the cost of having a very generic cache. The Item struct is pretty fat because of features like tracking/refCounting, delayed promotions, per item sizing, layered caching and so on. Not sure how to solve this without duplicating a ton of code and adding a TrackingCache and TrackingLayeredCache and every possible permutation...

from ccache.