potiuk commented on code in PR #25121:
URL: https://github.com/apache/airflow/pull/25121#discussion_r924524172


##########
docs/apache-airflow/howto/dynamic-dag-generation.rst:
##########
@@ -140,3 +140,74 @@ Each of them can run separately with related configuration
 
 .. warning::
   Using this practice, pay attention to "late binding" behaviour in Python 
loops. See `that GitHub discussion 
<https://github.com/apache/airflow/discussions/21278#discussioncomment-2103559>`_
 for more details
+
+
+Optimizing DAG parsing delays during execution
+----------------------------------------------
+
+Sometimes when you generate a lot of Dynamic DAGs from a single DAG file, it 
might cause unnecessary delays
+when the DAG file is parsed during task execution. The impact is a delay 
before a task starts.
+
+Why is this happening? You might not be aware but when your task is executed 
just before execution,
+Airflow parses the Python file the DAG comes from.
+
+The Airflow Scheduler (or DAG Processor) requires loading of a complete DAG 
file to process all metadata.
+However, task execution requires only a single DAG object to execute a task. 
Knowing this, we can
+skip the generation of unnecessary DAG objects when task is executed, 
shortening the parsing time.
+Upon evaluation of a DAG file, command line arguments are supplied which we 
can use to determine which
+Airflow component performs parsing:
+
+* Scheduler/DAG Processor args: ``["airflow", "scheduler"]`` or ``["airflow", 
"dag-processor"]``
+* Task execution args: ``["airflow", "tasks", "run", "dag_id", "task_id", 
...]``
+
+
+When tasks are executed, parsing time of dynamically generated DAGs when a 
task is executed can be optimized.
+
+However, depending on the executor used and forking model, those args might be 
available via ``sys.args``
+or via name of the process running. Airflow either executes tasks via running 
a new Python interpreter or
+sets the name of the process as "airflow task supervisor: {ARGS}".
+
+This optimization is most effective when the number of generated DAGs is high.

Review Comment:
   I shortened it a bit more - the optimization part was already mentioned 
above.



-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to