Agent Idle Profile

This benchmark measures the background resource footprint of a Forge Agent running in idle mode.

The objective is to quantify the cost of keeping a provider node online.

---

Test Configuration

Container limits:

CPU limit: 0.5 vCPU
Memory limit: 256 MB

Observation window:

180 seconds
Sampling interval: 10 seconds

---

Measured

Observed steady state:

Memory usage: ~21–23 MB
CPU usage: typically <2%
Process count: ~13

Initial startup spike is excluded from steady state measurements.

---

Interpretation

Forge Agents are designed to remain resident on provider machines without interfering with normal workloads.

Typical idle resource usage remains well below container limits.

---

Provider Implications

Providers can keep nodes online continuously without significant impact on host usability.

This enables opportunistic compute participation without dedicating machines exclusively to Forge workloads.