On September 15, 2026, all Cloud Composer 1 and Cloud Composer 2 version 2.0.x environments will reach their planned end of life, and you will not be able to use them. We recommend planning migration to Cloud Composer 3.
Follow the instructions on this page to enable or disable DAG serialization.
In a Cloud Composer environment, both the Airflow scheduler and
the Airflow web server continuously process DAGs. You can improve
the reliability and performance of the Airflow web server by enabling
DAG serialization.
Enabling DAG serialization forces the scheduler to process DAG files
before they are sent to the web server. The web server does not process DAGs.
Instead, it reads the serialized DAGs from the Airflow database. Serializing
DAGs in this way reduces the CPU and memory usage of the web server,
especially when processing a large number of DAGs.
Before you begin
DAG serialization affects the following Cloud Composer features:
Enabling DAG serialization disables all Airflow web server plugins for
Cloud Composer. This does not impact scheduler or worker plugins,
including Airflow operators, sensors, and so on.
Enabling DAG serialization
You can enable DAG serialization for an existing environment or when creating a
new environment.
To enable DAG serialization,
override the following Airflow configuration options:
Section
Key
Value
core
store_serialized_dags
True
core
store_dag_code
True
core
min_serialized_dag_update_interval
30
scheduler
dag_dir_list_interval
30
The min_serialized_dag_update_interval
Airflow configuration option controls how frequently serialized DAGs
are updated in the database.
The dag_dir_list_interval
option controls how frequently removed DAGs are deleted from the Airflow
database. A high update frequency can negatively impact performance. We
recommend setting min_serialized_dag_update_interval and
dag_dir_list_interval to 30 seconds.
Disabling DAG serialization
You can enable DAG serialization for an existing environment or when creating
a new environment.
To disable DAG serialization, override the following Airflow
configuration options:
[[["Easy to understand","easyToUnderstand","thumb-up"],["Solved my problem","solvedMyProblem","thumb-up"],["Other","otherUp","thumb-up"]],[["Hard to understand","hardToUnderstand","thumb-down"],["Incorrect information or sample code","incorrectInformationOrSampleCode","thumb-down"],["Missing the information/samples I need","missingTheInformationSamplesINeed","thumb-down"],["Other","otherDown","thumb-down"]],["Last updated 2025-08-08 UTC."],[[["\u003cp\u003eDAG serialization in Cloud Composer improves the reliability and performance of the Airflow web server by having the scheduler process DAG files before they are sent, reducing the web server's CPU and memory usage.\u003c/p\u003e\n"],["\u003cp\u003eStarting with Cloud Composer version 1.15.0, DAG serialization is enabled by default, and it can be managed by overriding Airflow configuration options in both new and existing environments.\u003c/p\u003e\n"],["\u003cp\u003eEnabling DAG serialization requires setting the \u003ccode\u003estore_serialized_dags\u003c/code\u003e and \u003ccode\u003estore_dag_code\u003c/code\u003e Airflow configuration options to \u003ccode\u003eTrue\u003c/code\u003e, along with recommended settings of \u003ccode\u003e30\u003c/code\u003e for both \u003ccode\u003emin_serialized_dag_update_interval\u003c/code\u003e and \u003ccode\u003edag_dir_list_interval\u003c/code\u003e.\u003c/p\u003e\n"],["\u003cp\u003eDisabling DAG serialization involves overriding the \u003ccode\u003estore_serialized_dags\u003c/code\u003e and \u003ccode\u003estore_dag_code\u003c/code\u003e Airflow configuration options and setting them to \u003ccode\u003eFalse\u003c/code\u003e.\u003c/p\u003e\n"],["\u003cp\u003eDAG serialization is incompatible with asynchronous DAG loading and will disable all Airflow web server plugins, although scheduler and worker plugins remain unaffected.\u003c/p\u003e\n"]]],[],null,[]]
