[ https://issues.apache.org/jira/browse/FLINK-31772?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Danny Cranmer updated FLINK-31772: ---------------------------------- Fix Version/s: (was: 1.16.2) (was: 1.18.0) (was: 1.17.1) > AsyncSinkWriter Performance regression due to AIMD rate limiting strategy > ------------------------------------------------------------------------- > > Key: FLINK-31772 > URL: https://issues.apache.org/jira/browse/FLINK-31772 > 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 > Priority: Major > Labels: pull-request-available > Fix For: aws-connector-4.2.0 > > Attachments: Screenshot 2023-04-11 at 12.56.10.png, Screenshot > 2023-04-11 at 12.58.09.png, Screenshot 2023-04-11 at 13.01.47.png, Screenshot > 2023-04-17 at 13.02.31.png, Screenshot 2023-04-17 at 13.03.24.png, Screenshot > 2023-04-17 at 13.03.34-1.png, Screenshot 2023-04-17 at 13.03.34.png > > > 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)