[
https://issues.apache.org/jira/browse/SAMZA-1011?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Xinyu Liu updated SAMZA-1011:
-----------------------------
Description: This metric can be ambiguous in the new AsyncRunLoop. When
running in the single thread mode, it means the time spent on
task.processAsync(), window() and commit(), while in multithreading mode it
will be the time spent on scheduling the tasks operations. So we need to figure
out a better way to report it. (was: This metric can be ambiguous in the new
AsyncRunLoop. When running in the single thread mode, it means the time spent
on task.processAsync(), window() and commit(), while in multithreading mode it
will be the time spent on scheduling the tasks operations. So we should remove
it from the AsyncRunLoop.)
> Better report event loop utilization metrics in AsyncRunLoop
> ------------------------------------------------------------
>
> Key: SAMZA-1011
> URL: https://issues.apache.org/jira/browse/SAMZA-1011
> Project: Samza
> Issue Type: Bug
> Affects Versions: 0.11.0
> Reporter: Xinyu Liu
> Assignee: Xinyu Liu
> Priority: Minor
> Labels: newbie++
>
> This metric can be ambiguous in the new AsyncRunLoop. When running in the
> single thread mode, it means the time spent on task.processAsync(), window()
> and commit(), while in multithreading mode it will be the time spent on
> scheduling the tasks operations. So we need to figure out a better way to
> report it.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
