As I explained in the situation when the write-behind queue is full a Thread that updates a cache and propagates the changes into the write-behind store can be used to flush the write-behind queue since the queue is full. This situation can affect the performance especially if this happens too often.
— Denis > On Jun 3, 2016, at 11:30 AM, amitpa <[email protected]> wrote: > > Danis, > > Thanks. I am trying that. > > However shouldnt the write behinds not impact the GRID performance at all. > Since we are writing in write behin dmode to avoid the cost of slow disk IO. > I understand that theres a limit, but shouldnt this thread pool be different > if technically possible, allowing ignite to continue processing in case of > slow write behind performance. > > > > -- > View this message in context: > http://apache-ignite-users.70518.x6.nabble.com/Ignite-Write-Behind-performance-tp5385p5400.html > Sent from the Apache Ignite Users mailing list archive at Nabble.com.
