Re: Question on On-Heap Caching

Hi Naresh, One way to reduce latency is to use data collocation and send compute tasks for this data: https://apacheignite.readme.io/docs/affinity-collocation instead of gathering data from several data nodes on client node, you can collocate data required for you task on one node and send compu

Re: Question on On-Heap Caching

Hi Dmitriy, 1.We are accessing the data using key-value API's (getAll()) 2. Our data is partitioned in a three server node cluster, but our testcase primarily requests the data through one specific node. Regards, Naresh -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: Question on On-Heap Caching

With Ignite 2+, I have found that the on-heap option makes only modest improvements to performance in most cases. Likewise for copyOnRead=false, which works in conjunction with on-heap. These options work best in the case where you have a small number of cache entries that are read many times. In b

Re: Question on On-Heap Caching

Naresh, several questions: 1. How are you accessing data, with SQL or key-value APIs? 2. Are you accessing data locally on the server or remotely from a client? If remotely, then you might want to enable near caching. D. On Thu, Nov 9, 2017 at 3:01 PM, naresh.goty wrote: > Thanks Alex

Re: Question on On-Heap Caching

Thanks Alexey for the info. Actually our application is read-heavy, and we are seeing high latencies (based on our perf benchmark) when we are measuring the response times during load tests. Based on the one of the thread's recommendations (http://apache-ignite-users.70518.x6.nabble.com/10X-decreas

Re: Question on On-Heap Caching

Hi, Ignite always stores data off-heap. Enabling on-heap caching just turns Java heap into a cache for the off-heap memory, allowing you to configure eviction policies specific for such a heap cache. I believe the idea is tha

Question on On-Heap Caching

Hi All, We enabled on-heap caching for our application, as per documentation. The only change required is to set OnheapCacheEnabled property of CacheConfiguration. Once we made this change, and started up our application, ignite metrics still shows onheap and offheap memory. Note: we are using