Re: Question on On-Heap Caching

[colinc]

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
benchmarks, I've seen performance gains of around 30% for this type of
scenario.



--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: Question on On-Heap Caching

[Dmitriy Setrakyan]

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 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-
> decrease-in-performance-with-Ignite-2-0-0-td12637.html#a12655),
> we are trying to check if onheap cache have any reduction in latencies. But
> we did not see any noticeable difference in perf using onheap cache
> enabled/disabled. We are using ignite v2.3.
>
> Thanks,
> Naresh
>
>
>
> --
> Sent from: http://apache-ignite-users.70518.x6.nabble.com/
>

Re: Question on On-Heap Caching

[naresh.goty]

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-decrease-in-performance-with-Ignite-2-0-0-td12637.html#a12655),
we are trying to check if onheap cache have any reduction in latencies. But
we did not see any noticeable difference in perf using onheap cache
enabled/disabled. We are using ignite v2.3.

Thanks,
Naresh



--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: Question on On-Heap Caching

[Alexey Kukushkin]

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 that in some cases accessing on-heap is faster than
accessing off-heap, although I never saw any benchmarks or recommendations
what data access scenarios would benefit from the on-heap caching. Remember
that storing data on-heap negatively impacts GC. Maybe community will help.
You can also benchmark your use case with on-heap caching and without it
and share results with the community.