[ 
https://issues.apache.org/jira/browse/KAFKA-3769?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15340672#comment-15340672
 ] 

ASF GitHub Bot commented on KAFKA-3769:
---------------------------------------

GitHub user guozhangwang opened a pull request:

    https://github.com/apache/kafka/pull/1530

    KAFKA-3769: Create new sensors per-thread in KafkaStreams

    

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/guozhangwang/kafka K3769-per-thread-metrics

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/kafka/pull/1530.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #1530
    
----
commit 8a8efa52bc5538ba933f85a0cdb9196d4a222e10
Author: Guozhang Wang <wangg...@gmail.com>
Date:   2016-06-20T23:02:34Z

    use per-thread sensor names

commit 25859f4b5121e19602741809c18864d99a84574f
Author: Guozhang Wang <wangg...@gmail.com>
Date:   2016-06-20T23:02:40Z

    Merge branch 'trunk' of https://git-wip-us.apache.org/repos/asf/kafka into 
K3769-per-thread-metrics

commit 5fae56123fabc0568a99c27ba5b2e792b9f6a685
Author: Guozhang Wang <wangg...@gmail.com>
Date:   2016-06-20T23:29:47Z

    remove unused imports

----


> 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)

Reply via email to