jason810496 commented on code in PR #53183:
URL: https://github.com/apache/airflow/pull/53183#discussion_r2217754983
##########
airflow-core/docs/administration-and-deployment/dagfile-processing.rst:
##########
@@ -168,31 +168,31 @@ When you know what your resource usage is, the
improvements that you can conside
actions like increasing number of parsing processes might bring improvements
in performance at the
expense of higher utilization of those.
* increase hardware capacity (for example if you see that CPU is limiting you
or that I/O you use for
- DAG filesystem is at its limits). Often the problem with DAG processor
performance is
+ Dag filesystem is at its limits). Often the problem with Dag processor
performance is
simply because your system is not "capable" enough and this might be the
only way, unless a shared database
or filesystem is a bottleneck.
-* experiment with different values for the "DAG processor tunables". Often you
might get better effects by
+* experiment with different values for the "Dag processor tunables". Often you
might get better effects by
simply exchanging one performance aspect for another. For example if you
want to decrease the
- CPU usage, you might increase file processing interval (but the result will
be that new dags will
+ CPU usage, you might increase file processing interval (but the result will
be that new Dags will
appear with bigger delay). Usually performance tuning is the art of
balancing different aspects.
-* sometimes you change DAG processor behavior slightly (for example change
parsing sort order)
+* sometimes you change Dag processor behavior slightly (for example change
parsing sort order)
in order to get better fine-tuned results for your particular deployment.
-DAG processor Configuration options
+Dag processor Configuration options
"""""""""""""""""""""""""""""""""""
-The following config settings can be used to control aspects of the Scheduler.
-However, you can also look at other non-performance-related scheduler
configuration parameters available at
-:doc:`../configurations-ref` in the ``[scheduler]`` section.
+The following config settings can be used to control aspects of the Dag
processor.
+However, you can also look at other non-performance-related Dag processor
configuration parameters available at
+:doc:`../configurations-ref` in the ``[dag_processor]`` section.
- :ref:`config:dag_processor__file_parsing_sort_mode`
- The scheduler will list and sort the DAG files to decide the parsing order.
+ The Dag processor will list and sort the Dag files to decide the parsing
order.
- :ref:`config:dag_processor__min_file_process_interval`
- Number of seconds after which a DAG file is re-parsed. The DAG file is
parsed every
- min_file_process_interval number of seconds. Updates to dags are reflected
after
+ Number of seconds after which a Dag file is re-parsed. The Dag file is
parsed every
+ ``min_file_process_interval`` number of seconds. Updates to Dags are
reflected after
Review Comment:
```suggestion
:ref:`config:dag_processor__min_file_process_interval` number of seconds.
Updates to Dags are reflected after
```
Would adding config reference for `min_file_process_interval` be better ?
--
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]
