Hey!
Overall, if SLA permits, we generally recommend savepoint upgrades for
prod, you may use configure the `kubernetes.operator.savepoint.format.type`
to NATIVE to get close to checkpoint performance on your savepoints.
If the job is not running savepoint upgrades by default fall back to
"last-st
Hi Gyula,
Thanks for answering my questions!
>Savepoint upgrades on the other hand would generate a new job id (at least
after a recent fix on operator main).
Yes, the savepoint can help. However, IMO savepoint is not ideal compared
with checkpoints because of 1) performance concern: savepoint doe
There is no golden egg in the RocksDB tuning area but it can help a
significantly.
As a general rule the RocksDB state backend requires mainly 2 things to
perform well, memory and fast local storage.
You can tune these depending on the bottleneck and make measurements.
Memory is used as a cache a
