You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "Ahmed Hamdy (Jira)" <ji...@apache.org> on 2023/04/20 17:38:00 UTC
[jira] [Updated] (FLINK-31872) Add Support for Configuring AIMD Ratelimiting strategy parameters by Sink users for KinesisStreamsSink
[ https://issues.apache.org/jira/browse/FLINK-31872?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Ahmed Hamdy updated FLINK-31872:
--------------------------------
Summary: Add Support for Configuring AIMD Ratelimiting strategy parameters by Sink users for KinesisStreamsSink (was: CLONE - AsyncSinkWriter Performance regression due to AIMD rate limiting strategy)
> Add Support for Configuring AIMD Ratelimiting strategy parameters by Sink users for KinesisStreamsSink
> ------------------------------------------------------------------------------------------------------
>
> 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
> Priority: Major
> Labels: pull-request-available
> 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)