You are viewing a plain text version of this content. The canonical link for it is here.
Posted to jira@kafka.apache.org by "Xavier Léauté (Jira)" <ji...@apache.org> on 2019/08/20 22:45:00 UTC

[jira] [Updated] (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:all-tabpanel ]

Xavier Léauté updated KAFKA-8806:
---------------------------------
    Description: 
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 25% of CPU time spent in {{KafkaConsumer.poll()}}, when before it only represented less than 5%.

Most of the extra time appears to be spent in {{KafkaConsumer.validateOffsetsIfNeeded()}}, which did not show up in previous profiles.

  was:
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 25% 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.


> 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 25% of CPU time spent in {{KafkaConsumer.poll()}}, when before it only represented less than 5%.
> 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
(v8.3.2#803003)