Hi While doing scale testing we observed that FSStatebackend is out performing RocksDB. When using RocksDB, off heap memory keeps growing over a period of time and after a day pod got terminated with OOM.
Whereas the same data pattern FSStatebackend is running for days without any memory spike and OOM. Based on documentation this is what i understood: When the state size is so huge that we can't keep it in memory, that case RocksDB is preferred. That means indirectly when FSStatebackend is performing poorly when state size grows, RocksDB is preferred, right? Another question, We have run production using RocksDB for quite some time, if we switch to FSStatebackend, then what are the consequences? Following is what i can think of: Very first time i'll lose the state Thereafter w.r.t Save Points and Checkpoints the behavior is same ( I know there is no incremental checkpoint, but its a performance purpose) Other than that, do I see any issues? Regards Bhaskar
