CPU load
UnknownCollecting sampleInfrastructure / Capacity planning
Know the ceiling before you reach it.
Measured server health and conservative campaign budgets in one operational view.
ConnectingWaiting for server
Current capacity is unknown. Do not use the last sample as permission to add campaigns.
Memory used
UnknownCollecting sampleDisk used
UnknownCollecting sampleActive capacity
-Current headroom unknownMeasured CPU usage
Campaigns + Traffic Boost
Separate workload usage, combined load, and capacity left after all server work.
CampaignsUnknownWaiting for a complete CPU sample
Traffic BoostUnknownWaiting for a complete CPU sample
Combined loadUnknownWaiting for a complete CPU sample
CPU availableUnknownRemaining capacity is not known yet
Other server use: UnknownTotal server load: Unknown CPU measurements refresh every five seconds
Campaign CPU includes its workers and browser processes. Boost CPU includes Boost browser processes. Shared app work, databases, other services and CPU waits are counted once under Other server use. CPU available includes all of these loads; browser slots and memory can still limit new work.
| Campaign | Level | Open browsers | Waiting / resting | CPU cores | Server CPU |
|---|---|---|---|---|---|
| Waiting for Traffic Boost measurements. | |||||
Waiting workers have no browser yet. Open browsers can use little CPU while waiting on the network; resting workers have closed their browser. Short Boost visits are measured before shutdown so their CPU is retained in the next sample.
Safe active count now
-Measured headroom plus currently activeSafe campaigns to add
-Minimum of CPU, RAM, disk, and worker limitsSaved / queued
-Saved campaigns consume no browser budget until activeOperator guidance
Refresh required before using admission recommendations.Routing, resource model and infrastructure details
Adaptive routing / Shared execution
Browser work avoided and pooled
Browser-only domains are cached for 15–60 minutes, then probed again. Every active journey still receives an isolated proxy-bound browser context.
Redirect-first captures-Collecting
Browser fallbacks-Collecting
Natural-click journeys-Source-page DOM clicks with Referer evidence
Shared worker tasks-Collecting
100-campaign CPU target-Use at least 8 vCPU for 100 browser-required campaigns
Fallback reasonsNo browser fallback recorded yet
Measured configuration
Server and services
- Server
- -
- Operating system
- -
- CPU
- -
- Logical / effective cores
- -
- Total RAM
- -
- Total disk
- -
- Server uptime
- -
- Node runtime
- -
Leader (unknown / stale)PostgreSQL (unknown / stale)Redis (unknown / stale)Residential proxy (unknown / stale)
Configured guardrails
Execution limits
- Dashboard active limit
- -
- Local browser workers
- -
- Browser concurrency
- -
- Total concurrency
- -
- Total request ceiling
- -
- Campaign launch gap
- -
- Full launch spread
- -
- Shared Node workers
- -
- Reserved memory floor
- -
- Required free disk
- -
Measured components
Where memory and space are going
ComponentCPUMemoryStorage / countState
Control process PID ----Online (unknown / stale)
Active browser budget Planning model---Blocked (unknown / stale)
PostgreSQL Durable state---Offline (unknown / stale)
Redis Queue coordination---Offline (unknown / stale)
Active evidence Measured files---Measured (unknown / stale)
Campaign decisions
Active campaign resource deck
CPU and RAM are conservative planning budgets. Evidence size, runtime, PID, and port are measured.
| Campaign | Runtime | Process | Gateway | CPU budget | RAM budget | Evidence |
|---|---|---|---|---|---|---|
| No active campaigns match this view, or the sample is unavailable. | ||||||