Memory leak when initializing multiple instances about ristretto HOT 4 CLOSED

Thanks @awishformore and @karlmcguire .

Seems there was no leaking, 8G was the actual amount of memory needed given the config like that. The 150MB was just because Go's GC is fast enough to recycle it right away when the cache instance never leaves its local scope.

Closing now.

from ristretto.

Looks like cache.Close() is not sufficiently releasing memory.

from ristretto.

Hi @karlmcguire, I work with @zhangchiqing, and there was some implicit behaviour that made it hard to identify the problem was on our side. However, going through the ristretto code, it's possible the documentation is inaccurate on the NumCounters parameter. Taking into account the bloom filter, I think I came out at a memory usage that is about 4x what the comment on that parameter claims (2 bytes per entry)?

from ristretto.

@awishformore That sounds about right. We have since added multiple counter "rows" (currently 4, which is standard) with seeds for a 2-3% hit ratio increase. I will update the documentation.

from ristretto.