kafka-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (KAFKA-3769) KStream job spending 60% of time writing metrics
Date Fri, 10 Jun 2016 19:39:21 GMT

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

ASF GitHub Bot commented on KAFKA-3769:

GitHub user guozhangwang opened a pull request:


    KAFKA-3769: Optimize metrics recording overhead


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

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

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


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

    This closes #1490
commit 68c889e1cba59280e4c1a37007efcdec6c784878
Author: Guozhang Wang <wangguoz@gmail.com>
Date:   2016-06-10T17:50:29Z

    reduce time.milliseconds

commit ad5403c919fe6ee9e5c5e7e3d9c9f2534a5a3717
Author: Guozhang Wang <wangguoz@gmail.com>
Date:   2016-06-10T19:38:05Z

    use milliseconds instead of nanoseconds for state store metrics


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

View raw message