Skip to content

Performance and concurrency ​

Start with limits matching available model and AgentBox quotas. More workers do not increase external service quotas.

SettingScope
MAX_CONCURRENT_SESSIONSOrpheus execution capacity
max_concurrent_runsConcurrent runs per Mattermost workflow
MAX_PARALLEL_THREADSConnector thread-processing concurrency
MAX_CONCURRENT_REVIEWSConcurrent GitLab MR reviews
message_batch_windowGroup nearby messages before starting

One session executes one run at a time. Independent sessions can run concurrently.

Multiple API and worker instances must share the database, credential-store configuration, allowlist and encryption key. Settings that affect admission must match. Do not configure different capacity limits across one installation.

Run one Mattermost connector per source: server and bot identity. Independent sources can use separate processes. Increasing replicas for the same source is not a scaling method.

The GitLab review connector also runs as one instance per GitLab installation and bot identity. Adjust its concurrency limit without adding replicas for the same bot.

When latency grows, inspect active work, account quotas, sandbox preparation errors and company API response times. Mattermost recovery uses bounded history windows and gives live events priority over archive recovery.