> Performance is definitely improving. However, the worry is whether or not > OffHeap will be cleaned up properly and whether memory leaks will be caused > by the cache meta information of the Ignite Java Heap. > > Do you have any other concerns?
There is nothing I’m concerned about here. — Denis > On Oct 21, 2017, at 7:57 AM, dark <ekdxhrl0...@gmail.com> wrote: > > Thank you for your kind comments. > > EagerTttl is usually useful. However, it did not match our situation. > > We put 40k/s entry to ignite server node. If the backup option is enabled to > prevent some loss of data, large cache entries will cause simultaneous > expiration. (We expiry the Cache entry after 5 minutes without updating.) At > this time, Eager's 500ms interval and 1000 expiry was not enough to continue > the expiry efficiently, and there was an issue that keeps the > ttl-cleanup-worker CPU. So we chose to keep Cache itself on time, destroy > the cache itself and eliminate expiration costs. > > <http://apache-ignite-users.70518.x6.nabble.com/file/t1415/before_cpu.png> > < Before : EagerTtl is true > > > <http://apache-ignite-users.70518.x6.nabble.com/file/t1415/after_cpu.png> > < After : EagerTtl is false & cache destroy strategy > > > Performance is definitely improving. However, the worry is whether or not > OffHeap will be cleaned up properly and whether memory leaks will be caused > by the cache meta information of the Ignite Java Heap. > > Do you have any other concerns? > > Thanks again for your reply. :) > > > > > > -- > Sent from: http://apache-ignite-users.70518.x6.nabble.com/
