13 questions in one Jev call
Run a regulatory briefing as one batched Jev request instead of 13 singles.
Research- Cost
- 12.2x cheaper than 13 single-question calls
- Latency
- 10.0x faster than sequential singles
- Result
- Same answers under both batching strategies
Jev evaluates questions in parallel against one state. Adding questions barely changes the round trip.
The cookbook asks the same 13 questions five times as singles and five times as one batch. Answers stay the same. Cost and latency do not.
This is the batching case in the Jev directory: one request per document, not one request per question.
Pipeline
- Load the pinned GDPR Wikipedia article as state
- Ask 8 nouls, 2 choices, and 3 scores together
- Compare with 13 separate calls on the same article
Builder: TypeSafe cookbook. Stack: jev.