At a glance
- Did you know
- Batch jobs process large data sets on a schedule rather than per request.
- Rule of thumb
- Checkpoint progress so a failed job resumes instead of starting over.
- Watch out
- Jobs pile up; retries re-run side effects.
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
- Job scheduler: every job at the top of the minute A distributed job scheduler runs 150 jobs a second on average, but every 10 seconds the cron schedules line up and 5× as many fire at once.
- Web crawler: fetchers wait on slow sites A crawler fetches 300 pages a second. A fetch takes about 300 ms (slow sites, politeness delays), and there are 60 fetcher slots.
- The eval run eats the production quota An agent product serves 20 chats a second on one provider key with 6 million input tokens a minute. A CI regression gate runs the eval suite on the same key: 2 eval tasks a second, 20 model calls each, 4,000 tokens a call.
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.