You are viewing a plain text version of this content. The canonical link for it is here.
Posted to jira@kafka.apache.org by "Mayank Shekhar Narula (Jira)" <ji...@apache.org> on 2024/02/06 15:15:00 UTC
[jira] [Updated] (KAFKA-16226) Java client: Performance regression in Trogdor benchmark with high partition counts
[ https://issues.apache.org/jira/browse/KAFKA-16226?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Mayank Shekhar Narula updated KAFKA-16226:
------------------------------------------
Summary: Java client: Performance regression in Trogdor benchmark with high partition counts (was: Performance regression in Trogdor benchmark with high partition counts)
> Java client: Performance regression in Trogdor benchmark with high partition counts
> -----------------------------------------------------------------------------------
>
> Key: KAFKA-16226
> URL: https://issues.apache.org/jira/browse/KAFKA-16226
> Project: Kafka
> Issue Type: Bug
> Components: clients
> Reporter: Mayank Shekhar Narula
> Assignee: Mayank Shekhar Narula
> Priority: Major
> Fix For: 3.6.2, 3.8.0, 3.7.1
>
>
> Background
> https://issues.apache.org/jira/browse/KAFKA-15415 implemented optimisation in java-client to skip backoff period if client knows of a newer leader, for produce-batch being retried.
> What changed
> The implementation introduced a regression noticed on a trogdor-benchmark running with high partition counts(36000!).
> With regression, following metrics changed on the produce side.
> 1. record_queue_time_avg
> Regression Details
> Fix
--
This message was sent by Atlassian Jira
(v8.20.10#820010)