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

Yu-Lin Chen commented on YUNIKORN-2088:
---------------------------------------

Hi [~chia7712] ,
{code:java}
BTW, a trivial comment: It seems to me the resource bar which fires the 
mouseover event should keep the opacity. Instead, we should change the opacity 
of other resource bars; after all, the resource bar onto which we move the 
cursor is what we want to observe.{code}
Actually I think your idea is great. If no one has any objections to this 
change, I will create a subtask for it tomorrow.



!demo for new hovering behavior.gif!

 

> [umbrella] Node utilisation chart per partition and resource type
> -----------------------------------------------------------------
>
>                 Key: YUNIKORN-2088
>                 URL: https://issues.apache.org/jira/browse/YUNIKORN-2088
>             Project: Apache YuniKorn
>          Issue Type: Improvement
>          Components: core - common, webapp
>            Reporter: Wilfred Spiegelenburg
>            Assignee: Yu-Lin Chen
>            Priority: Major
>         Attachments: Add margin-top to Node Resource Utilization chart .png, 
> demo for new hovering behavior.gif, 截圖 2024-02-04 凌晨4.03.36.png
>
>
> Node utilisation is calculated based on a resource name. The bar chart can 
> only show one resource. The optimal solution would be to allow selecting a 
> resource to show in the bar chart via a drop down or show all resource types.
> Also need to look at the placing of the chart: the dashboard shows data not 
> linked to a partition we should consider moving the diagram to the nodes page 
> which is partition based to provide a better view.
> This is a major change of REST objects, endpoints etc



--
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