collinmcnulty commented on issue #41620: URL: https://github.com/apache/airflow/issues/41620#issuecomment-2307792486
I think the selected task would be the entry point, and for DAGs larger than some configured number of tasks, the Graph view should not load unless a specific task is selected from the Grid view. Or maybe you just pick any random root node and display that one. Navigation would be like it is now, that you can pan around the graph, and my clicking on a task it will change the center point, loading the new tasks as required and dropping old ones. So you can traverse the graph by clicking successive tasks to move around the graph. I work in support for Astronomer, so I'm speaking on behalf of users I've worked with, not for my own DAGs. I've observed that DAGs that are large and don't make great use of task groups exist in the wild, and there is the problem that on shared Airflow instances, even one DAG like this can start breaking the webserver for everyone. I'm certainly open to other ideas on how to make graph view efficient, but I don't think we can/should rely on DAG authors to keep graph view efficiency in mind when writing DAGs. -- 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]
