Hello! Oops, I was wrong. This is indeed the wrong setting.
Have you tried specifying evictionPolicy? I think it is the one that controls eviction from onheap cache. You can put a LruEvictionPolicy of 100 000 here, for example. Regards, -- Ilya Kasnacheev пн, 8 июл. 2019 г. в 17:09, Andrey Dolmatov <itdolma...@gmail.com>: > No, because we didnt specify QueryEntity. > Does onheapCacheEnabled uses for SQL only? > What default value for sqlOnheapCacheMaxSize? > > пн, 8 июл. 2019 г. в 17:05, Ilya Kasnacheev <ilya.kasnach...@gmail.com>: > >> Hello! >> >> Have you tried also specifying sqlOnheapCacheMaxSize? You can specify 100 >> 000 if you like. >> >> Regards, >> -- >> Ilya Kasnacheev >> >> >> пн, 8 июл. 2019 г. в 17:01, Andrey Dolmatov <itdolma...@gmail.com>: >> >>> We use simple replicated KV cache. >>> We try to upload 32 000 000 small records <Long, Long> to it (about 6Gb >>> in data region, persistance disabled). We load data using DataStreamer. >>> >>> If we set onheapCacheEnabled=false, server node consumes heap about 500 >>> Mb. >>> If we set onheapCacheEnabled=true, server node consumes heap about 6 Gb. >>> >>> Why DataStreamer uses heap memory to load data? Why on-heap size is >>> unlimited (not just 100.000 records)? What default on-heap eviction policy? >>> >>> <bean class="org.apache.ignite.configuration.CacheConfiguration"> >>> >>> <property name="cacheMode" value="REPLICATED"/> >>> <property name="onheapCacheEnabled" value="true"/> >>> <property name="copyOnRead" value="false"/> >>> >>> Thanks! >>> >>
