ignite-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Alexey Goncharuk <alexey.goncha...@gmail.com>
Subject Re: Ignite Write Behind performance
Date Fri, 03 Jun 2016 17:53:47 GMT
Ignite _does_ use a separate thread pool to persist data in write-behind
mode, this is the essential difference between write-through and
write-behind. However, if your cache load rate is significantly higher than
the database insert rate, the write queue will grow faster than background
threads can flush data, so eventually you will get an OOME.

In this situation you can
 - block and wait until there is some space in the write queue
 - persist your own data synchronously
Ignite choses the second option and writes transaction data synchronously.

As Denis pointer out, you should tune write-behind parameters to make sure
that background threads are working at sufficient insert rate. Also make
sure that you use batched inserts in your CacheStore implementation.

Hope this helps,

2016-06-03 10:26 GMT-07:00 amitpa <amitpa@nrifintech.com>:

> I understood this perfectly.
> What I mean is :-
> Shouldnt the write behind use a separete thread pool so that slow write
> behind process does not impact the whole grid ?
> --
> View this message in context:
> http://apache-ignite-users.70518.x6.nabble.com/Ignite-Write-Behind-performance-tp5385p5412.html
> Sent from the Apache Ignite Users mailing list archive at Nabble.com.

View raw message