[jira] [Updated] (KAFKA-5661) Develop and understanding of how to tune transactions for optimal performance
[ https://issues.apache.org/jira/browse/KAFKA-5661?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matthias J. Sax updated KAFKA-5661: --- Fix Version/s: (was: 2.2.0) > Develop and understanding of how to tune transactions for optimal performance > - > > Key: KAFKA-5661 > URL: https://issues.apache.org/jira/browse/KAFKA-5661 > Project: Kafka > Issue Type: Sub-task >Affects Versions: 0.11.0.0 >Reporter: Apurva Mehta >Assignee: Apurva Mehta >Priority: Major > > Currently, we don't have an idea of the throughput curve for transactions > across a different range of workloads. > Thus we would like to understand how to tune transactions so that they are > viable across a broad range of work loads. For instance, what knobs can you > tweak if you use small messages to yet get acceptable transactional > performance? We don't understand the performance curve across variables like > message size, batch size, transaction duration, linger.ms, etc., and it would > be good to get an understanding of this area and publish recommended > configurations for different workloads. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (KAFKA-5661) Develop and understanding of how to tune transactions for optimal performance
[ https://issues.apache.org/jira/browse/KAFKA-5661?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dong Lin updated KAFKA-5661: Fix Version/s: (was: 2.1.0) 2.2.0 > Develop and understanding of how to tune transactions for optimal performance > - > > Key: KAFKA-5661 > URL: https://issues.apache.org/jira/browse/KAFKA-5661 > Project: Kafka > Issue Type: Sub-task >Affects Versions: 0.11.0.0 >Reporter: Apurva Mehta >Assignee: Apurva Mehta >Priority: Major > Fix For: 2.2.0 > > > Currently, we don't have an idea of the throughput curve for transactions > across a different range of workloads. > Thus we would like to understand how to tune transactions so that they are > viable across a broad range of work loads. For instance, what knobs can you > tweak if you use small messages to yet get acceptable transactional > performance? We don't understand the performance curve across variables like > message size, batch size, transaction duration, linger.ms, etc., and it would > be good to get an understanding of this area and publish recommended > configurations for different workloads. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (KAFKA-5661) Develop and understanding of how to tune transactions for optimal performance
[ https://issues.apache.org/jira/browse/KAFKA-5661?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rajini Sivaram updated KAFKA-5661: -- Fix Version/s: (was: 2.0.0) 2.1.0 > Develop and understanding of how to tune transactions for optimal performance > - > > Key: KAFKA-5661 > URL: https://issues.apache.org/jira/browse/KAFKA-5661 > Project: Kafka > Issue Type: Sub-task >Affects Versions: 0.11.0.0 >Reporter: Apurva Mehta >Assignee: Apurva Mehta >Priority: Major > Fix For: 2.1.0 > > > Currently, we don't have an idea of the throughput curve for transactions > across a different range of workloads. > Thus we would like to understand how to tune transactions so that they are > viable across a broad range of work loads. For instance, what knobs can you > tweak if you use small messages to yet get acceptable transactional > performance? We don't understand the performance curve across variables like > message size, batch size, transaction duration, linger.ms, etc., and it would > be good to get an understanding of this area and publish recommended > configurations for different workloads. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (KAFKA-5661) Develop and understanding of how to tune transactions for optimal performance
[ https://issues.apache.org/jira/browse/KAFKA-5661?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Damian Guy updated KAFKA-5661: -- Fix Version/s: (was: 1.1.0) 1.2.0 > Develop and understanding of how to tune transactions for optimal performance > - > > Key: KAFKA-5661 > URL: https://issues.apache.org/jira/browse/KAFKA-5661 > Project: Kafka > Issue Type: Sub-task >Affects Versions: 0.11.0.0 >Reporter: Apurva Mehta >Assignee: Apurva Mehta >Priority: Major > Fix For: 1.2.0 > > > Currently, we don't have an idea of the throughput curve for transactions > across a different range of workloads. > Thus we would like to understand how to tune transactions so that they are > viable across a broad range of work loads. For instance, what knobs can you > tweak if you use small messages to yet get acceptable transactional > performance? We don't understand the performance curve across variables like > message size, batch size, transaction duration, linger.ms, etc., and it would > be good to get an understanding of this area and publish recommended > configurations for different workloads. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (KAFKA-5661) Develop and understanding of how to tune transactions for optimal performance
[ https://issues.apache.org/jira/browse/KAFKA-5661?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guozhang Wang updated KAFKA-5661: - Fix Version/s: (was: 1.0.0) 1.1.0 > Develop and understanding of how to tune transactions for optimal performance > - > > Key: KAFKA-5661 > URL: https://issues.apache.org/jira/browse/KAFKA-5661 > Project: Kafka > Issue Type: Sub-task >Affects Versions: 0.11.0.0 >Reporter: Apurva Mehta >Assignee: Apurva Mehta > Fix For: 1.1.0 > > > Currently, we don't have an idea of the throughput curve for transactions > across a different range of workloads. > Thus we would like to understand how to tune transactions so that they are > viable across a broad range of work loads. For instance, what knobs can you > tweak if you use small messages to yet get acceptable transactional > performance? We don't understand the performance curve across variables like > message size, batch size, transaction duration, linger.ms, etc., and it would > be good to get an understanding of this area and publish recommended > configurations for different workloads. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
