Longer (5 vs 0.2s) guard_cycle for Django-Q

To reduce average CPU load. Given paperless is mostly idling and when not, just spawns long-running operations (e.g., OCR), a 0.2s health-check of the Django-Q cluster is unnecessary. See also #1084

diff --git a/src/paperless/settings.py b/src/paperless/settings.py
index c512b1d47c247ca6594f1d06dab094c0b13b1981..9a5d9453d771366834e5e2dcb4423e81bc44e316 100644 (file)
--- a/src/paperless/settings.py
+++ b/src/paperless/settings.py
@@ -458,6 +458,7 @@ PAPERLESS_WORKER_RETRY: Final[int] = __get_int(
 
 Q_CLUSTER = {
     "name": "paperless",
+    "guard_cycle": 5,
     "catch_up": False,
     "recycle": 1,
     "retry": PAPERLESS_WORKER_RETRY,