Problems / Agents and tools, easy

Agent model out of streams

Agents hold a model stream for about 2 s per step. The deployment allows 30 streams; agents need about 50.

Free to open. Runs in your browser, no sign-up.

Your goals

Success ≥ 95% of tasks, p99 ≤ 90 s.

4 requests a second for 45 seconds: 100% task (writes).

What each component does in this design, and what calls it. The simulator mimics each one from these settings.

Component	Its job here	Settings
Load balancerLoad balancer	Traffic enters here.Calls Agent API.Layer 4 balancers route by IP and port; layer 7 balancers read HTTP and can route by path or header.	–
Agent APIApp service	Load balancer forwards to it.Calls Agent orchestrator.Little's law: throughput ≈ concurrency ÷ latency. 200 slots at 50 ms serve about 4,000 req/s.	3 replicas × 500 slots · timeout 180 s
Agent orchestratorAgent orchestrator	Agent API calls it.Calls Model, MCP tool servers.An agent loops: think, call a tool, read the result, repeat until done.	400 slots · 6 steps
ModelLLM endpoint	Agent orchestrator calls it.Latency has two parts: time to the first token, then a steady stream of tokens per second.	30 streams
MCP tool serversTool / MCP server	Agent orchestrator calls it.Tools give the model actions such as search or database queries; each call is another round trip.	200 slots

Try it first. Open one hint at a time if you get stuck.

Hint 1

Streams in use = model calls a second × seconds per call.

Hint 2

Agent work multiplies: tasks a second × steps per task = calls a second on every tool the loop uses.

One way to solve it

Raise the model’s concurrent streams.