Hi lmark58 -
I met a problem similar with you have met before. The performance of
_cache.get()_ gets worse when enabled the write-behind, so I want to know
will the performance got better when disabling the WriteBehindCoalescing?
--
Sent from:
Alexey,
I dug into this a bit more and it is the perfect storm of the way the write
behind works and the way we are using one of our Caches. We need to keep
our kafka offsets persisted, so we have a cache with the Key being a topic
and partition. When we get a record from that combination we
Alexey,
With our use case setting the coalesce off will probably make it worse, for
at least some caches we are doing many updates to the same key, one of the
reasons I am setting the batch size to 500.
I will send the cachestore implementation and some logs that show the
phenomenon early next
Hi,
Can you share your cache store implementation?
It could be several reasons for possible performance degradation in
write-behind mode.
Ignite can start flushing your cache values in main() thread if cacheSize
becomes greater than 1,5 x setWriteBehindFlushSize. It is a common case but
it does
