joshzana opened a new issue, #23772: URL: https://github.com/apache/airflow/issues/23772
### Apache Airflow version 2.3.0 (latest released) ### What happened I upgraded a local dev deployment of Airflow from 2.2.5 to 2.3.0, then loaded the new `/dags/<dag_id>/grid` page for a few dag ids. On a big DAG, I’m seeing 30+ second latency on the `/grid` API, followed by a 10+ second delay each time I click a green rectangle. For a smaller DAG I tried, the page was pretty snappy. I went back to 2.2.5 and loaded the tree view for comparison, and saw that the `/tree/` endpoint on the large DAG had 9 seconds of latency, and clicking a green rectangle had instant responsiveness. This is slow enough that it would be a blocker for my team to upgrade. ### What you think should happen instead The grid view should be equally performant to the tree view it replaces ### How to reproduce Generate a large DAG. Mine looks like the following: - 900 tasks - 150 task groups - 25 historical runs Compare against a small DAG, in my case: - 200 tasks - 36 task groups - 25 historical runs The large DAG is unusable, the small DAG is usable. ### Operating System Ubuntu 20.04.3 LTS (Focal Fossa) ### Versions of Apache Airflow Providers _No response_ ### Deployment Docker-Compose ### Deployment details Docker-compose deployment on an EC2 instance running ubuntu. Airflow web server is nearly stock image from `apache/airflow:2.3.0-python3.9` ### Anything else Screenshot of load time: <img width="1272" alt="image" src="https://user-images.githubusercontent.com/643593/168957215-74eefcb0-578e-46c9-92b8-74c4a6a20769.png"> GIF of click latency:  ### Are you willing to submit PR? - [ ] Yes I am willing to submit a PR! ### Code of Conduct - [X] I agree to follow this project's [Code of Conduct](https://github.com/apache/airflow/blob/main/CODE_OF_CONDUCT.md) -- 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]
