At a glance
- Did you know
- Agent memory keeps facts across sessions so the agent does not start from scratch.
- Rule of thumb
- Store short summaries rather than raw transcripts, and let memories expire.
- Watch out
- Write amplification; poisoned memories.
Its settings in ScaleMySystems
What you can change on it in the lab, and what each number does.
- Concurrency (slots)
- Calls it can work on at once (per instance when autoscaling). Needed slots ≈ calls per second × seconds each takes. Extra calls wait in the queue, then are rejected.
- Queue capacity
- Calls allowed to wait for a free slot. A bigger queue absorbs bursts but adds waiting time; 0 rejects straight away.
- vCPU
- CPU cores available. Needed ≈ calls per second × CPU per request ÷ 1000. Above about 90% busy it slows down and may crash.
- CPU per request (ms)
- CPU time each call burns. Part of what the component is; make the code cheaper to lower it.
- Latency (p50) (ms)
- Typical time one call takes here, before any calls it makes itself. Slots are held for this long.
- Latency (p99) (ms)
- The slowest 1% of calls. Callers must set their timeout above this or they cut off healthy calls.
- Timeout to dependencies (ms)
- How long it waits for each call it makes before giving up. Set it above the dependency’s p99 but low enough that a dead dependency does not hold every slot.
- Error rate
- Share of calls that fail on their own (bugs, declines, flaky tools). An agent that calls it on every step multiplies this.
- Quota (req/min)
- Calls allowed per minute (an API key or provider limit). Calls over it get 429s. Needed = calls per second × 60, with headroom.
Problems that start with it
- MCP agent platform 4 tasks/s. The agent thinks (model) and acts (tools through an MCP gateway) 6 times per task, with vector memory and results in S3.
- Ten steps of MCP tools Agents call MCP tools 10 times per task. A 1% tool error rate becomes a 10% task failure rate.
- Agent memory on a small store The agent reads and writes long-term memory every step, on a memory store with 2 slots and 60 ms per call.
- Deep research: from launch build to real traffic A multi-agent research product on its first servers: the lead agent fans each question out to sub-agents that search and browse the web, and the browser tool, sub-agent pool and model capacity are an eighth of their real size. Questions arrive one a second and each takes minutes. One in ten fails.
Full lesson coming soon
Lessons are being added one component at a time: how it works, its settings, a live exercise to break and fix it, interview questions and a short check. See the Circuit breaker lesson for what one looks like.