Re: Write Behind slowing down performance greatly

2021-06-07 Thread Ilya Korol
Yes, you're right. There is no remote listeners. I mean do you use only local listener or also configured remote filters? (Excuse me for being not clear enough). Did you configure backups for cache partitions? If so at which node you are listening for event (primary or backup)? Try to initia

Re: Write Behind slowing down performance greatly

2021-06-07 Thread gigabot
Hi I'm using a local listener ( Is there any other type?). I can't share a reproducer because of workplace restrictions. I am seeing data that was put via another node, so I'm not clear what you mean about remote node puts not being visible. The documentation here https://ignite.apache.org/docs/la

Re: Write Behind slowing down performance greatly

2021-06-07 Thread Ilya Korol
What kind of listener you used? Could you share your configuration or link to a reproducer? I've checked write behind feature with mysql instance and don't find any performance loss (i receive cache put events instantly via registered listener but they appear in DB with configured time skew/ba

Write Behind slowing down performance greatly

2021-06-03 Thread gigabot
I observed that turning on writeThrough with writeBehind slows down performance(i.e. time data reaches listeners) greatly. I tried setting the flush frequency to 0 and the flush size to 1 billion, and so the flushes are not even happening yet, and still the performance is slow. I am wondering wh