Hello! All cache values are now always stored off-heap, on-heap is only used as cache (on top of cache).
1. You should check if performance is good enough without on-heap caching. 2. You should have some constant amount of RAM for heap (4G is allright, but it depends) and dedicate the rest of memory to off-heap (by configuring default DataRegion). This unless you have a lot of on-heap caching. Regards, -- Ilya Kasnacheev вс, 9 дек. 2018 г. в 14:32, Isaeed Mohanna <isae...@gmail.com>: > Hi > I have moved from Ignite 1.9.0 to Ignite 2.6.0. > Part of my implementation I generate many objects and store them in a cache > and later a task process them, these objects are usually destroyed after > processing they live for ~1 minutes and i have around 2K of them each cycle > (1min) , but very few of them live for weeks. > In Ignite 1.9.0 these were stored in the Java Heap and in the new Version > 2.6.0 be default they are stored offheap. > 1. Based on the scenario i described should my cache be stored off-heap? or > should it be stored on-heap for faster creation\deletion? > 2. If i should store off-heap how much memory (%) should i keep for the > Java > heap? > Thanks in advance > > > > -- > Sent from: http://apache-ignite-users.70518.x6.nabble.com/ >
