You are viewing a plain text version of this content. The canonical link for it is here.
Posted to jira@kafka.apache.org by "Richard Yu (JIRA)" <ji...@apache.org> on 2019/08/16 22:24:00 UTC
[jira] [Commented] (KAFKA-8806) Kafka.poll spends significant
amount of time in KafkaConsumer.updateAssignmentMetadataIfNeeded
[ https://issues.apache.org/jira/browse/KAFKA-8806?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16909445#comment-16909445 ]
Richard Yu commented on KAFKA-8806:
-----------------------------------
[~vvcephei] Since you wrote this part of the code, your thoughts on this?
> Kafka.poll spends significant amount of time in KafkaConsumer.updateAssignmentMetadataIfNeeded
> ----------------------------------------------------------------------------------------------
>
> Key: KAFKA-8806
> URL: https://issues.apache.org/jira/browse/KAFKA-8806
> Project: Kafka
> Issue Type: Bug
> Affects Versions: 2.3.0
> Reporter: Xavier Léauté
> Assignee: David Arthur
> Priority: Major
>
> Comparing the performance profile of 2.2.0 and 2.3.0, we are seeing significant performance differences in the {{KafkaConumer.updateAssignmentMetadataIfNeeded()}} method.
> The call to {{KafkaConsumer.updateAssignmentMetadataIfNeeded()}} now represents roughly 40% of CPU time spent in {{KafkaConsumer.poll()}}, when before it only represented less than 2%.
> Most of the extra time appears to be spent in {{KafkaConsumer.validateOffsetsIfNeeded()}}, which did not show up in previous profiles.
--
This message was sent by Atlassian JIRA
(v7.6.14#76016)