[ 
https://issues.apache.org/jira/browse/IMPALA-13233?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Surya Hebbar closed IMPALA-13233.
---------------------------------

> Represent phases of each instance separately on the webUI's query timeline
> --------------------------------------------------------------------------
>
>                 Key: IMPALA-13233
>                 URL: https://issues.apache.org/jira/browse/IMPALA-13233
>             Project: IMPALA
>          Issue Type: New Feature
>            Reporter: Surya Hebbar
>            Assignee: Surya Hebbar
>            Priority: Major
>         Attachments: bucketed_phases_with_tooltips.png, 
> large_no_of_instances_parallell_representation.png, 
> large_profile_no_borders_334307144a03276f_e184c3ea00000000_timeline.html, 
> large_profile_with_borders_cd4932da98382a06_40c2221b00000000_timeline.html, 
> no_borders_6a477079d908e96d_03bfee1d00000000_timeline.html, 
> small_no_of_instances_parallell_representation.png, 
> timeline_representation.png, 
> with_borders_6a477079d908e96d_03bfee1d00000000_timeline.html
>
>
> Currently, in the query timeline, each instance's phases are represented 
> together in a single bar with dividers to show when each phase has finished.
> This results in several problems as follows.
>  * If phases of multiple instances end at the same time, it is often hard or 
> impossible to distinguish.
>  * Huge profiles with a large number of instances produce mostly black lines, 
> which would not be desired by the user.
>  * In the case of multiple instances, each phase overlaps the next, hence 
> blocking the user from realizing that other instances have started with the 
> next phase.
>  * The correlation between representation and the actual values is less.
> So, it would be preferable to represent each instance's phases separately.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to