; Please provide a simple program which could reproduce this so that we can
> help you more.
>
> Best
> Yun Tang
> --
> *From:* Aljoscha Krettek
> *Sent:* Tuesday, June 16, 2020 19:53
> *To:* user@flink.apache.org
> *Subject:* Re: Improved p
2020 19:53
To: user@flink.apache.org
Subject: Re: Improved performance when using incremental checkpoints
Hi,
it might be that the operations that Flink performs on RocksDB during
checkpointing will "poke" RocksDB somehow and make it clean up it's
internal hierarchies of storage more. Other
20 15:44
*To:* user@flink.apache.org
*Subject:* Improved performance when using incremental checkpoints
Hello,
We are using RocksDB as the backend state.
At first we didn't enable the checkpoints mechanism.
We observed the following behaviour and we are wondering why ?
When using the rocksDB *
day, June 16, 2020 15:44
> *To:* user@flink.apache.org
> *Subject:* Improved performance when using incremental checkpoints
>
> Hello,
>
> We are using RocksDB as the backend state.
> At first we didn't enable the checkpoints mechanism.
>
> We observed the following beh
this problem.
Best
Yun Tang
From: nick toker
Sent: Tuesday, June 16, 2020 15:44
To: user@flink.apache.org
Subject: Improved performance when using incremental checkpoints
Hello,
We are using RocksDB as the backend state.
At first we didn't enable the checkpoints
Hello,
We are using RocksDB as the backend state.
At first we didn't enable the checkpoints mechanism.
We observed the following behaviour and we are wondering why ?
When using the rocksDB *without* checkpoint the performance was very
extremely bad.
And when we enabled the checkpoint the
