You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@kafka.apache.org by "Jay Kreps (JIRA)" <ji...@apache.org> on 2016/06/01 05:23:12 UTC
[jira] [Commented] (KAFKA-3769) KStream job spending 60% of time
writing metrics
[ https://issues.apache.org/jira/browse/KAFKA-3769?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15309288#comment-15309288 ]
Jay Kreps commented on KAFKA-3769:
----------------------------------
Nice catch.
> KStream job spending 60% of time writing metrics
> ------------------------------------------------
>
> Key: KAFKA-3769
> URL: https://issues.apache.org/jira/browse/KAFKA-3769
> Project: Kafka
> Issue Type: Bug
> Components: streams
> Affects Versions: 0.10.0.0
> Reporter: Greg Fodor
> Assignee: Guozhang Wang
> Priority: Critical
>
> I've been profiling a complex streams job, and found two major hotspots when writing metrics, which take up about 60% of the CPU time of the job. (!) A PR is attached.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)