kaxil commented on code in PR #60804: URL: https://github.com/apache/airflow/pull/60804#discussion_r3083383630
########## airflow-core/docs/faq.rst: ########## @@ -677,8 +677,28 @@ How to prevent API server memory growth? The API server caches serialized Dag objects in memory. Over time, as Dag versions accumulate (see :ref:`faq:dag-version-inflation`), this cache grows and can consume several gigabytes of memory. -The recommended solution (available since Airflow 3.2.0) is to use **gunicorn** with **rolling worker -restarts**. Gunicorn periodically recycles worker processes, releasing all accumulated memory. It also +There are two complementary approaches: + +**1. Bounded DAG caching (available since Airflow 3.2.0)** Review Comment: Fixed -- caching section now says 3.3.0, gunicorn section stays 3.2.0. ########## uv.lock: ########## Review Comment: Related -- the uv.lock diff is from adding `cachetools>=6.0.0` as a direct dependency in airflow-core's pyproject.toml. It was already a transitive dep via google-auth, but we pin it explicitly now. -- 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]
