Hi, Most likely your write-behind Threads can’t keep up with volume of data that is aggregated in the write-behind buffer and you get with the situation when from time to time writing to the DB is performed in the sync mode from system Thread(s). I would suggest you playing with the following write-behind configuration to avoid the situation above: - CacheConfiguration.setWriteBehindFlushSize - increase size of the write-behind buffer; - CacheConfiguration.setWriteBehindFlushThreadCount; - CacheConfiguration.setWriteBehindFlushFrequence - decrease this value triggering the flushing more frequently. Default value is 5 seconds.
— Denis > On Jun 2, 2016, at 7:23 PM, amitpa <[email protected]> wrote: > > Hello, > > I am struggling with improving ignite transaction performance. However this > is another problem > > However if I am doing write behind and the writes are slow, I am seeing that > the over all performance of teh grid drops. > > Is there any configuration that I can do to make ignite performance stable > even when the writes are being slow in write behind (due to slow DB) > > Currently I have 10 threads in write behind mode. > > What should be my system threadpool size assuming I have two caches which > participate in transactions and 2 nodes in 10G network. > > > > > > > > -- > View this message in context: > http://apache-ignite-users.70518.x6.nabble.com/Ignite-Write-Behind-performance-tp5385.html > Sent from the Apache Ignite Users mailing list archive at Nabble.com.
