Hi Rick, 1) As for now, there is no API for checking write-behind queue size. In any case, such method would provide only an approximate result. 2) You should carry out some testing to figure out the appropriate balance between the batch size and flush frequency that will fit your particular case.There is no rule of thumb and each particular case should be treated specifically. If the underlying DB is able to cope with a high write rate then you could try setting a decent batch size and flush frequency size <times> * <avg DB write rate>, where <times> depends on your cache-to-DB synchronization requirements.
Kind regards, Alex -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/
