Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Calendar view is taking too long to load in airflow 2.3.0 #23602

Closed
1 of 2 tasks
potiuk opened this issue May 9, 2022 Discussed in #23545 · 5 comments
Closed
1 of 2 tasks

Calendar view is taking too long to load in airflow 2.3.0 #23602

potiuk opened this issue May 9, 2022 Discussed in #23545 · 5 comments
Labels
affected_version:2.3 Issues Reported for 2.3 area:UI Related to UI/UX. For Frontend Developers. area:webserver Webserver related Issues kind:bug This is a clearly a bug

Comments

@potiuk
Copy link
Member

potiuk commented May 9, 2022

Discussed in #23545

Originally posted by sambhatt25 May 6, 2022

Apache Airflow version

2.3.0 (latest released)

What happened

Calendar view in DAG is taking too long to load. It was fine in 2.2.5.

What you think should happen instead

No response

How to reproduce

No response

Operating System

MacOS 12.3

Versions of Apache Airflow Providers

No response

Deployment

Other 3rd-party Helm chart

Deployment details

No response

Anything else

No response

Are you willing to submit PR?

  • Yes I am willing to submit a PR!

Code of Conduct

@potiuk
Copy link
Member Author

potiuk commented May 9, 2022

Details in #23545 but it looks like the calendar DAG is indeed slow with high-frequency DAGs. likely because of sequential retrieval with latency.

@bbovenzi
Copy link
Contributor

bbovenzi commented May 9, 2022

We'd have to look out how the "planned" part of calendar view is calculated.

@eladkal eladkal added area:UI Related to UI/UX. For Frontend Developers. affected_version:2.3 Issues Reported for 2.3 and removed pending-response area:core labels May 9, 2022
@bbovenzi
Copy link
Contributor

Yes, so here we're just iterating through every single next_dagrun_info for a whole year. We should be able to interpret the schedule better than that.

UI-wise we could split the requests to show at least something to the user, but really, we need to improve the webserver code.

@jedcunningham
Copy link
Member

#24262 is an attempted optimization for cron scheduled DAGs.

@bbovenzi
Copy link
Contributor

bbovenzi commented Jun 9, 2022

I think the PR above should be enough to close this.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
affected_version:2.3 Issues Reported for 2.3 area:UI Related to UI/UX. For Frontend Developers. area:webserver Webserver related Issues kind:bug This is a clearly a bug
Projects
None yet
Development

No branches or pull requests

4 participants