Hi Mike - Thanks for the reply. Please take a look at the point to point details.
Ignite need to sync memory and disk time to time, if you write rate is bigger than disk speed that means Ignite will never able to sync memory and disk, that's why it starts to throttle your writes. ---- Its a write intensive process and I am curious if there way to figure out what is the disk speed that is required in terms of IOPS (AWS) other than programmatically instrumenting it. You can disable throttling, which I don't recommend, because then, instead of throttling updates, ignite can completely stop all updates during a checkpoint. --- Ageed. If i disable throttling it will get into this stop the world checkpoints. Not good i guess. here are several options you can try, first use different physical disks for WAL/WAL Archive and Storage.(WAL and WAL archive should on the same disk). If it won't help then it's time to scale. --- Storage and WAL are different disks . Wal Archive is same as Wal So if it's AWS like environment, I would recommend using IO1 disks with high IOPS to make sure that it can handle your peak load. However, IO1 disks it's pretty expensive might be it would be more efficient to just add a few more nodes. ---- io1 disks are not an option as they will shoot up the cost. May be adding few more nodes is an option and i will check on this. Again, if it's just initial data load, then it can be fine to have throttling because usually, initial data load creates load significantly bigger then regular load. --- In a way its initial load but the subsequent also we have significant throughput requirements. -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/
