CSE Roadmap

Core tier · about 4 hours · 11 parts

Part 8 of 11 · 2 min read

Mistakes that waste a split

Common mistakes, and what the example does not do.

Mistakes that waste a split

  • Splitting by job title ("researcher", "writer", "reviewer") instead of by independence.
  • Counting only the orchestrator's tokens.
  • Ignoring the shared-context tax, so every worker loads a 10,000-token background.
  • Parallelising a chain, and then paying for relays.
  • Assuming more agents means more accuracy without a baseline.
  • Forgetting the cache when comparing with a single agent.
  • Passing facts through the orchestrator as free text (module 8 of Level 7).

What the example does not do

About this example What the example does not do
  • No models. Reliability uses hazard rates chosen for the example; the direction comes from module 6, and the values are assumed.
  • A simple graph. Each sub-task depends on at most its three predecessors; real dependency graphs have other shapes.
  • Equal sub-tasks. All have the same size; real ones vary, and the slowest sets the latency.
  • No retries, no failures, no tool latency.
  • Optional real-model experiment: pick ten tasks that you can label as parallel or coupled, run each as a single agent and as an orchestrator with workers, and record accuracy, total tokens from the usage field, and wall-clock time.

Check yourself

Eight sub-tasks, each needing the output of the one before. Does splitting them across eight agents make the task faster?

Show answer

No. A full chain was 1.46 times slower than one agent in the model, because each handoff adds a step and a chance to lose a fact. Split by independence, not by job title.

For the curious Why the answer depends on the prompt cache

With no cache, eight independent workers used 0.45 of the single agent tokens. With a cache that makes one long context cheap, the same split used 0.87, and with two sub-tasks it cost more than one agent (1.44). Every size and rate here is an assumption chosen to show the shape, so treat the direction as the lesson.

What you will use daily at work

Practice What it looks like
Start with one agent Add a second only when the task, the tools or the coordination outgrow one.
Count the dependencies Many edges between sub-tasks means many handoffs, and each can lose a fact.
Measure cost and latency both A split can cut one and raise the other.