[jira] [Created] (FLINK-31872) CLONE - AsyncSinkWriter Performance regression due to AIMD rate limiting strategy

["Ahmed Hamdy (Jira)" <ji...@apache.org>]

Ahmed Hamdy created FLINK-31872:
-----------------------------------

             Summary: CLONE - AsyncSinkWriter Performance regression due to AIMD rate limiting strategy
                 Key: FLINK-31872
                 URL: https://issues.apache.org/jira/browse/FLINK-31872
             Project: Flink
          Issue Type: Bug
          Components: Connectors / Common, Connectors / Firehose, Connectors / Kinesis
    Affects Versions: 1.16.0, aws-connector-3.0.0, 1.16.1, aws-connector-4.0.0, aws-connector-4.1.0
            Reporter: Ahmed Hamdy
            Assignee: Ahmed Hamdy
             Fix For: 1.16.2, 1.18.0, 1.17.1, aws-connector-4.2.0


h1. Issue

While benchmarking the {{KinesisStreamSink}} for 1.15 against the legacy {{FlinkKinesisProduced}} , it is observed that the new sink has a performance regression against the deprecated sink for same environment setting.

Further investigation identified that the AIMD Ratelimiting strategy is the bottleneck for the regression. 

Attached results for {{KinesisStreamSink}}  against {FlinkKinesisProducer} and {KinesisStreamSink} after disabling {{AIMDRatelimitingStrategy}}



h2. Environment Settings
- Benchmarking was performed on AWS KDA.
- Application logic is just sending records downstream
- Application parallelism was tested to be 1.
- Kinesis stream number of shards was tested with 8 and 12.
- payload size was 1Kb and 100Kb.

 



--
This message was sent by Atlassian Jira
(v8.20.10#820010)