[
https://issues.apache.org/jira/browse/AIRFLOW-2529?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16498398#comment-16498398
]
ASF subversion and git services commented on AIRFLOW-2529:
----------------------------------------------------------
Commit 5f79465bd8be8b18cce85a8d40a48fdc6b8a81cf in incubator-airflow's branch
refs/heads/master from [~seelmann]
[ https://git-wip-us.apache.org/repos/asf?p=incubator-airflow.git;h=5f79465 ]
[AIRFLOW-2529] Improve graph view performance and usability
Limit number of dag runs shown in drop down. Add base date
and number of runs widgets known from other views which
allows kind of paging through all dag runs.
> Improve graph view performance and usability
> --------------------------------------------
>
> 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
> Assignee: Stefan Seelmann
> Priority: Major
> Fix For: 2.0.0
>
> Attachments: Screenshot_2018-05-28_21-32-38.png
>
>
> 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)
