[SAMZA-1011] Better report event loop utilization metrics in AsyncRunLoop

• Type: Bug
• Status: Resolved
• Priority: Minor
• Resolution: Won't Fix
• Affects Version/s: 0.11.0
• Labels: newbie++
• Assignee: Xinyu Liu
• Reporter: Xinyu Liu
• Created: 01/Sep/16 00:31
• Updated: 21/Nov/17 19:38
• Resolved: 21/Nov/17 19:38

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.