[
https://issues.apache.org/jira/browse/AIRFLOW-2762?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16547543#comment-16547543
]
Ash Berlin-Taylor commented on AIRFLOW-2762:
--------------------------------------------
A half way option (that doesn't involve having to store a dependency graph in
the DB -- though that might be useful for other reasons it's a lot more work)
is to take the list (i.e. the home page of the webserver) from the ORM, but the
detail view can load just the one specific DAG like this
https://github.com/apache/incubator-airflow/blob/d11593bebf9e5551bd8bd3941b528faf57cc19f4/airflow/api/common/experimental/trigger_dag.py#L89-L92
> Parallelize DAG parsing in webserver
> ------------------------------------
>
> Key: AIRFLOW-2762
> URL: https://issues.apache.org/jira/browse/AIRFLOW-2762
> Project: Apache Airflow
> Issue Type: Improvement
> Reporter: Kevin Yang
> Priority: Major
>
> Currently the webserver parses DagBag in a single thread fashion and causes
> the start up time to be slow when we have large # of DAG files. Webservers
> should not need the actual DAG object and this should be parallelized.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
