You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@samza.apache.org by "Yan Fang (JIRA)" <ji...@apache.org> on 2015/07/13 23:13:05 UTC

[jira] [Commented] (SAMZA-401) Add utilization metrics for the event loop

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

Yan Fang commented on SAMZA-401:
--------------------------------

[~depombo], one comment in the RB. But feel free to reject it. :)

> Add utilization metrics for the event loop
> ------------------------------------------
>
>                 Key: SAMZA-401
>                 URL: https://issues.apache.org/jira/browse/SAMZA-401
>             Project: Samza
>          Issue Type: Improvement
>          Components: metrics
>    Affects Versions: 0.8.0
>            Reporter: Yan Fang
>            Assignee: Luis De Pombo
>              Labels: newbie++
>         Attachments: SAMZA-401.patch, SAMZA-401.v2.patch
>
>
> As discussed [here|https://issues.apache.org/jira/browse/SAMZA-349?focusedCommentId=14116417&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-14116417],
> {quote}
> it would be useful to add "utilization" (aka "duty cycle") as a metric, which is the sum of all the timings divided by the window length. That can tell you how much idle time there is in the event loop (how much headroom before the job will start falling behind).
> {quote}
> It is useful to add this metric for the event loop.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)