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

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

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

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