Fluksio/app
0
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Warn at startup when worker or cascade limits are far past the cores

Browse Source 
More than four times os.cpu_count() logs one warning; the value is kept.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01WgBfkm4rCmtd1T4vHWjEPx
This commit is contained in:
stroblme
2026-10-15 09:51:38 +02:00
co-authored by Claude Opus 5.5
parent 025123a219
commit efe80cb3c2
4 changed files with 46 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files
docs/reference/configuration.md
+3 -1
View File
@@ -137,7 +137,9 @@ Set `TZ` in `.env` for schedules that should follow local time, such as
| `OBS_RETENTION_DAYS` | `30` | retention for metrics, events and run records |
The three concurrency limits must be at least `1`. They also have CLI flags:
`--max-workers`, `--max-cascades` and `--max-runs`. Resource flags are `--gpus`,
`--max-workers`, `--max-cascades` and `--max-runs`. When `FLOW_MAX_WORKERS` or
`FLOW_MAX_CASCADES` is more than four times the machine's core count, the
engine logs a warning at startup and uses the value anyway. Resource flags are `--gpus`,
`--ram` and `--worker-max-rss`.
Nodes with declared resources are scheduled against the available budget.