[ https://issues.apache.org/jira/browse/AIRFLOW-2529?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16492176#comment-16492176 ]
Tao Feng edited comment on AIRFLOW-2529 at 5/27/18 10:43 PM: ------------------------------------------------------------- Not sure if it is related, but we introduce a new config(default_dag_run_display_number) in [https://github.com/apache/incubator-airflow/pull/3279] which controls the numbers of dag-run to load in UI. was (Author: taofeng): Not sure if it is related, but we introduce a new config in [https://github.com/apache/incubator-airflow/pull/3279] which controls the numbers of dag-run to load in UI. > Graph View DAG Run dropdown > --------------------------- > > Key: AIRFLOW-2529 > URL: https://issues.apache.org/jira/browse/AIRFLOW-2529 > Project: Apache Airflow > Issue Type: Improvement > Components: webapp > Affects Versions: 1.9.0 > Reporter: Stefan Seelmann > Priority: Major > > The "Graph View" has a dropdown which contains all DAG run IDs. If there are > many (thousands) of DAG runs the page gets barely usable. It takes multiple > seconds to load the page because all DAG runs must be fetched from DB, are > processed, and a long option list is rendered in the browser. It is also not > very useful because in such a long list it is hard to find a particular DAG > run. > A simple fix to address the load time would be to just limit the number of > shown DAG runs. For example only the latest N are shown, N could be > "page_size" from airflow.cfg which is also used in other views. If the DAG > run that should be shown (via query parameters execution_date or run_id) is > not included in the N lastest list it can still be added by a 2nd SQL query. > A more complex change to improve usability would require a different way to > select a DAG run. For example a popup to search for DAG runs with pagination > etc. But such functionality already exits in the /dagrun UI. -- This message was sent by Atlassian JIRA (v7.6.3#76005)