RE: [EXTERNAL]Using RocksDBStateBackend and SSD to store states,
application runs slower..
CAUTION: This email originated from outside of the organization. Do not click
links or open attachments unless you can confirm the sender and know the
content is safe.
Hi,
using FLASH_SSD_OPTIMIZED alr
Hi,
using FLASH_SSD_OPTIMIZED already sets the number of threads to 4. This
optimization can improve the source throughput and reduce the delayed wrate
rate.
If this optimization didn't fix the back pressure, could you share more
information about your job? Could you check the metric of the back
Hi!
I'd try re-running the SSD test with the following config options:
state.backend.rocksdb.thread.num: 4
state.backend.rocksdb.predefined-options: FLASH_SSD_OPTIMIZED
On Thu, Jul 21, 2022 at 4:11 AM vtygoss wrote:
> Hi, community!
>
>
> I am doing some performance tests based on my scene.
>
Hi, community!
I am doing some performance tests based on my scene.
1. Environment
- Flink: 1.13.5
- StateBackend: RocksDB, incremental
- user case: complex sql contains 7 joins and 2 aggregation, input data
30,000,000 records and output 60,000,000 records about 80GB.
- resource: flink on ya
