You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@samza.apache.org by "Yi Pan (Data Infrastructure) (JIRA)" <ji...@apache.org> on 2016/05/25 00:27:13 UTC
[jira] [Commented] (SAMZA-951) Improve event loop timing metrics
[ https://issues.apache.org/jira/browse/SAMZA-951?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15299227#comment-15299227 ]
Yi Pan (Data Infrastructure) commented on SAMZA-951:
----------------------------------------------------
Merged and submitted. Thanks!
> Improve event loop timing metrics
> ---------------------------------
>
> Key: SAMZA-951
> URL: https://issues.apache.org/jira/browse/SAMZA-951
> Project: Samza
> Issue Type: Improvement
> Components: metrics
> Affects Versions: 0.10.1
> Reporter: Jake Maes
> Assignee: Jake Maes
> Priority: Minor
> Fix For: 0.10.1
>
> Attachments: SAMZA-951_1.patch, SAMZA-951_2.patch, SAMZA-951_3.patch
>
>
> SAMZA-401 added the event-loop-utilization metric to measure the % active time in the event loop. However, the value for the event-loop-utilization (at least since samza 10) is almost always ~= 1.0, even for over-provisioned jobs, which is not very useful.
> The way it is currently measured, the active time includes choose-ns which includes time spent in poll() waiting for new messages. This waiting should be considered idle time.
> The goals of this ticket are to:
> 1. Exclude the choose time from the active time to fix the event-loop-utilization metric.
> 2. Add deserialization-ns and poll-ns metrics to help users understand where the time is being spent in the chooser.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)