promptdojo_promptdojo_promptdojo_promptdojo_promptdojo_promptdojo_promptdojo_promptdojo_promptdojo_promptdojo_promptdojo_

Batch vs realtime serving — step 7 of 7

ch 46 · model serving, ci/cd, and mlopsch 46 · model serving, ci/cd, and mlopsch 46 · model serving, ci/cd, and mlopsch 46 · model serving, ci/cd, and mlopsch 46 · model serving, ci/cd, and mlopsch 46 · model serving, ci/cd, and mlopsch 46 · model serving, ci/cd, and mlopsch 46 · model serving, ci/cd, and mlopsch 46 · model serving, ci/cd, and mlopsch 46 · model serving, ci/cd, and mlopsch 46 · model serving, ci/cd, and mlops7/7
Checkpoint

One last thing before we move on. pass this to mark the lesson done, or skip and keep moving. hop to the next when you're ready.

Cost the three shapes for 10k requests/day: batch only = the $2 job; realtime = $5 baseline + $0.0001/request; hybrid = the $2 job + $0.00001/lookup. Print the three daily costs (:.2f), then the two verdict lines: "cheapest with per-user lookups: hybrid (batch can't serve lookups)" and f"realtime premium over hybrid: {ratio:.1f}x". The cost SHAPE (burst-then-zero vs always-on) is the table's bottom row, computed.

full-screen editor opens — close anytime to keep reading.

open the editor to run it.