rednaxelafx commented on PR #43307: URL: https://github.com/apache/spark/pull/43307#issuecomment-1755943552
A nice improvement to the UI 👍 But there's a dilemma: this feature is supposed to improve the UI's usability on large plans. For us it's quite common to have very large query plan graphs and the existing UI is already quite heavy (takes a while to render...). In that case this new feature might actually make the usability worse when a user clicks on a node and triggers a whole-graph update. Can we have either a Spark conf or a checkbox on the UI to allow users to opt-out of this feature when they find it counterproductive in their scenario? Side note: when I used to work on the HotSpot C2 compiler, I used the IdealGraphVisualizer (IGV) a lot to visualize the C2 IR. It also provides node selection and highlighting capabilities, and in addition it supports "node hiding" -- you can choose to focus on a subset of nodes and hide all of the other nodes, and optionally show the immediate neighbor nodes of the selected subgraph to be shown in lower opacity, and double-clicking on these neighbors will add them to the selection. It was super useful and my workflow was heavily dependent on that. I'd start out from the specific node in question and gradually expand out to cover enough context, and try to figure out what the problem was. In a graph of thousands of nodes this allowed me to work with mostly a couple dozen nodes at a time. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
