hermes-admin/hermes-agent
1
0
Fork 0
Code Issues Pull Requests Actions 28 Packages Projects Releases Wiki Activity

docs(gateway): state the real bound on concurrent turn threads

Browse Source 
The comment claimed turn concurrency is bounded at admission by
max_concurrent_sessions, but that defaults to unset and auto-resume is
uncapped. The real bound is one live turn per session plus turns
abandoned by the inactivity timeout, whose threads keep running. Say so,
and note in the max_concurrent_sessions docs that it is the only cap on
concurrent gateway turns.

Co-authored-by: Kyzcreig <9063726+Kyzcreig@users.noreply.github.com>
This commit is contained in:
kshitijk4poor
2026-09-26 18:34:49 +05:30
committed by kshitij
parent fb992c84bc
commit 1b00d0ad7b
2 changed files with 8 additions and 3 deletions
Download Patch File Download Diff File Expand all files Collapse all files

7
gateway/run.py
View File

@@ -59,9 +59,10 @@ _TELEGRAM_CONNECT_TIMEOUT_SECS_DEFAULT = 180.0
_TELEGRAM_INITIAL_CONNECT_TIMEOUT_SECS_DEFAULT = 45.0
_ADAPTER_DISCONNECT_TIMEOUT_SECS_DEFAULT = 5.0
# Size of the pool that runs turn bodies (blocking agent work). ``None`` = unbounded: a turn body
# holds its thread for the whole turn (every tool call blocks), so a finite pool silently queues
# turns that were already accepted behind whichever bodies are running, with nothing in the logs.
# Concurrency is bounded where turns are ADMITTED (``max_concurrent_sessions``), not here.
# holds its thread for the whole turn (every tool call blocks), so a finite pool silently queued
# already-accepted turns behind running ones. Actual bound: one live turn per session, plus turns
# abandoned by the inactivity timeout (run_turn keeps no handle; their thread runs to completion).
# ``max_concurrent_sessions`` is the only admission cap and is unset by default.
_TURN_MAX_WORKERS = None
# Size of the separate pool for best-effort session HOUSEKEEPING; why it is separate: _run_housekeeping_in_executor.
_HOUSEKEEPING_MAX_WORKERS = 4