Resource management (Vortexa 25% CPU cap)
Hard rules that prevent CPU spikes and keep the bot stable.
The host enforces a strict 25% CPU cap.
Design every feature like CPU is a paid resource.
Global loops: always stagger
Any global loop (broadcasts, status rotation, scheduled checks) must be staggered.
Rule: 10-second intervals minimum.
Implementation pattern:
setTimeout chains, not tight setInterval
or an async loop with await sleep(10_000)
Why: staggered work smooths load and avoids Vortexa throttling.
Per-message work: keep it O(1)
Do not scan channels, members, or messages on every count.
Do not recompute global state.
Validate, update, persist, exit.
Last updated