[
https://issues.apache.org/jira/browse/KAFKA-15402?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17887640#comment-17887640
]
Benoit Delbosc edited comment on KAFKA-15402 at 10/8/24 3:50 PM:
-----------------------------------------------------------------
Hi,
Any plan to have a consumer option to skip the {{maybeCloseFetchSessions}}
which, as I understand, is an optimization for memory footprint?
This is significantly impacting our unit tests duration, starting/stopping ~50
consumers takes 10 seconds per test.
This forces us to stay with the old 3.4.1.
Regards.
ben.
was (Author: bdelbosc):
Hi,
Any plan to have a consumer option to skip the {{maybeCloseFetchSessions}} that
is from my understanding just an optimization for memory footprint ?
Again this is impacting deeply our unit tests duration, starting/stopping ~50
consumers takes 10s per test, so we are forced to stay on old 3.4.1.
Regards.
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.6.0, 3.5.1
> Reporter: Benoit Delbosc
> Priority: Critical
> Labels: consumer-threading-refactor
> Fix For: 4.0.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)
