Seems I misunderstood your question. Did you disable both writeThrough and writeBehind properties and got worse perfomance?
On Wed, Apr 5, 2017 at 4:39 PM, Nikolai Tikhonov <[email protected]> wrote: > Hi, > > Yes, it's expected behavior. If you disable writeBehind then each update > will be propagated in underlying a store immediately and it's impact to > performance. You can find more details in docs [1]. > > 1. https://apacheignite.readme.io/docs/persistent- > store#section-write-behind-caching > > On Wed, Apr 5, 2017 at 4:09 AM, waterg <[email protected]> > wrote: > >> Hello all, >> >> I'm testing the effect of write behind and how it impacts the performance. >> I found that if I simply disable write behind by setting writeThrough and >> writeBehindEnabled property to false, my application performance is WORSE >> than before. Is it something expected? >> >> Thank you! >> >> >> >> >> -- >> View this message in context: http://apache-ignite-users.705 >> 18.x6.nabble.com/Disable-WriteBehind-tp11729.html >> Sent from the Apache Ignite Users mailing list archive at Nabble.com. >> > >
