[
https://issues.apache.org/jira/browse/KAFKA-15402?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18036785#comment-18036785
]
Benoit Delbosc edited comment on KAFKA-15402 at 11/10/25 10:50 AM:
-------------------------------------------------------------------
Hi Kirk, I confirm that I am looking for an option to skip the 'close session'
FETCH request that impacts response time by {{fetch.max.wait.ms}}.
I am using {{close()}} which should default to
{{close(Duration.ofSeconds(30))}}.
I will give a try with 0ms or something lower than {{fetch.max.wait.ms}} and
let you know.
Thanks for your feedback.
ben
was (Author: bdelbosc):
Hi Kirk, I confirm that I am looking for an option to skip the 'close session'
FETCH request that impacts response time by `fetch.max.wait.ms`.
I am using `close()` which should default to `close(Duration.ofSeconds(30))`.
I will give a try with 0ms or something lower than `fetch.max.wait.ms` and let
you know.
Thanks for your feedback.
ben
> Performance regression on close consumer after upgrading to 3.5.0
> -----------------------------------------------------------------
>
> Key: KAFKA-15402
> URL: https://issues.apache.org/jira/browse/KAFKA-15402
> Project: Kafka
> Issue Type: Bug
> Components: clients, consumer
> Affects Versions: 3.5.0, 3.5.1, 3.6.0
> Reporter: Benoit Delbosc
> Assignee: Kirk True
> Priority: Major
> Fix For: 4.2.0
>
> Attachments: image-2023-08-24-18-51-21-720.png,
> image-2023-08-24-18-51-57-435.png, image-2023-08-25-10-50-28-079.png
>
>
> Hi,
> After upgrading to Kafka client version 3.5.0, we have observed a significant
> increase in the duration of our Java unit tests. These unit tests heavily
> rely on the Kafka Admin, Producer, and Consumer API.
> When using Kafka server version 3.4.1, the duration of the unit tests
> increased from 8 seconds (with Kafka client 3.4.1) to 18 seconds (with Kafka
> client 3.5.0).
> Upgrading the Kafka server to 3.5.1 show similar results.
> I have come across the issue KAFKA-15178, which could be the culprit. I will
> attempt to test the proposed patch.
> In the meantime, if you have any ideas that could help identify and address
> the regression, please let me know.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
