Hard max cache size exceeded about bigcache HOT 6 CLOSED

Looks like golang #1670 was solved!

from bigcache.

Hi,

This issue is directly related with map implementation in go. I created a ticket for it on a go lang issue tracker. I don't know when it will be fixed, but I will try to take a look on map implementation in a free time, maybe I will be able to propose some solution.

from bigcache.

Hi @Freeaqingme

Thanks for submitting issue. At the first glance it looks weird. bigcache keeps one big array where all entries are stored. But we doesn't monitor size of internal map containing offset. Another thing that could make application eating so much memory is GC not freeing it — could you post your GC settings and GC log.

I hope I can create Minimal, Complete, and Verifiable example and debug this problem. If you already have it please share.

EDIT: I think good start is to extend caches_gc_overhead_comparsion.go compare memory footprint.

from bigcache.

I'm sorry for the delay. I think I was able to reproduce issue with this code

from bigcache.

I'm sorry for the delay as well. It's still on my list, but had some more urgent things coming up first. Having said that, if you're able to reproduce it then at least we have got the first step towards fixing it :)

from bigcache.

I am closing the issue as there is nothing to do in bigcache to solve it. There was presented a fix for golang map in a ticket which I created. It will be probably released in go version 1.8

from bigcache.