Cloud Composer 환경에서는 Airflow 스케줄러와 Airflow 웹 서버 모두 지속적으로 DAG를 처리합니다. DAG 직렬화를 사용 설정하면 Airflow 웹 서버의 신뢰성과 성능을 개선할 수 있습니다.
스케줄러가 DAG 파일을 웹 서버로 전송하기 전에 DAG 직렬화를 사용 설정하면 강제로 DAG 파일을 처리합니다. 웹 서버는 DAG를 처리하지 않습니다.
대신 Airflow 데이터베이스에서 직렬화된 DAG를 읽습니다. 이러한 방식으로 DAG를 직렬화하면 특히 많은 수의 DAG를 처리할 때 웹 서버의 CPU 및 메모리 사용량이 감소합니다.
min_serialized_dag_update_interval Airflow 구성 옵션은 직렬화된 DAG가 데이터베이스에서 업데이트되는 빈도를 제어합니다.
dag_dir_list_interval 옵션은 삭제된 DAG가 Airflow 데이터베이스에서 삭제되는 빈도를 제어합니다. 업데이트 빈도가 높으면 성능에 부정적인 영향을 줄 수 있습니다. min_serialized_dag_update_interval 및 dag_dir_list_interval은 30초로 설정하는 것이 좋습니다.
[[["이해하기 쉬움","easyToUnderstand","thumb-up"],["문제가 해결됨","solvedMyProblem","thumb-up"],["기타","otherUp","thumb-up"]],[["이해하기 어려움","hardToUnderstand","thumb-down"],["잘못된 정보 또는 샘플 코드","incorrectInformationOrSampleCode","thumb-down"],["필요한 정보/샘플이 없음","missingTheInformationSamplesINeed","thumb-down"],["번역 문제","translationIssue","thumb-down"],["기타","otherDown","thumb-down"]],["최종 업데이트: 2025-08-29(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,["# Enabling and disabling DAG serialization\n\n\u003cbr /\u003e\n\n\u003cbr /\u003e\n\n\u003cbr /\u003e\n\n\nCloud Composer 3 \\| Cloud Composer 2 \\| **Cloud Composer 1**\n\n\u003cbr /\u003e\n\nFollow the instructions on this page to enable or disable DAG serialization.\n\nIn a Cloud Composer environment, both the Airflow scheduler and\nthe Airflow web server continuously process DAGs. You can improve\nthe reliability and performance of the Airflow web server by enabling\n[DAG serialization](https://airflow.apache.org/docs/apache-airflow/stable/dag-serialization.html).\n\nEnabling DAG serialization forces the scheduler to process DAG files\nbefore they are sent to the web server. The web server does not process DAGs.\nInstead, it reads the serialized DAGs from the Airflow database. Serializing\nDAGs in this way reduces the CPU and memory usage of the web server,\nespecially when processing a large number of DAGs.\n\nBefore you begin\n----------------\n\n| **Note:** Starting from Cloud Composer version **1.15.0** , DAG serialization is enabled by default. You can enable and disable DAG serialization in new and existing environments by [overriding Airflow configuration options](/composer/docs/composer-2/override-airflow-configurations), as described in the following sections.\n\nDAG serialization affects the following Cloud Composer features:\n\n- DAG serialization cannot be enabled at the same time as [asynchronous DAG loading](/composer/docs/composer-2/access-airflow-web-interface#asynchronous-load).\n- 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.\n\nEnabling DAG serialization\n--------------------------\n\nYou can enable DAG serialization for an existing environment or when creating a\nnew environment.\n| **Note:** Do not apply these settings to environments running Airflow 2.x. The DAG serialization and storing DAG code in Airflow Metadata Database is by default turned on in Airflow 2.x and you cannot switch it on or off.\n\nTo enable DAG serialization,\n[override](/composer/docs/composer-2/override-airflow-configurations) the following Airflow configuration options:\n\nThe [`min_serialized_dag_update_interval`](https://airflow.apache.org/docs/stable/configurations-ref.html#min-serialized-dag-update-interval)\nAirflow configuration option controls how frequently serialized DAGs\nare updated in the database.\nThe [`dag_dir_list_interval`](https://airflow.apache.org/docs/stable/configurations-ref.html#dag-dir-list-interval)\noption controls how frequently removed DAGs are deleted from the Airflow\ndatabase. A high update frequency can negatively impact performance. We\nrecommend setting `min_serialized_dag_update_interval` and\n`dag_dir_list_interval` to 30 seconds.\n\nDisabling DAG serialization\n---------------------------\n\nYou can enable DAG serialization for an existing environment or when creating\na new environment.\n\nTo disable DAG serialization, [override](/composer/docs/composer-2/override-airflow-configurations) the following Airflow\nconfiguration options:"]]
