Skip to main content
Deployment & Operations

Batch Inference

Batch inference runs a model over a large set of inputs offline on a schedule — typically nightly or hourly — optimized for throughput and cost-per-prediction rather than latency.

AIDOLS Research Team · Editorial standards

Full definition

Batch jobs maximize hardware utilization by saturating GPUs with large input groups, often using cheap spot/preemptible compute. Outputs are written to a warehouse or feature store and later read by downstream services. Batch is the right choice when downstream consumers tolerate hours-old predictions — churn scoring, demand forecasting, lead scoring, marketing audience generation.

Why it matters

Teams default to online inference when batch would be far cheaper: batch jobs can run on spot capacity, which AWS discounts by up to 90% off On-Demand prices, and LLM providers such as Anthropic discount batch requests by 50%. A clean rule: if the consumer of a prediction does not need it within seconds, batch it. The savings often subsidize the higher-margin online use cases.

Example

A retailer scores all 40M customers nightly for churn risk in a 25-minute Spark job; the marketing platform reads results in the morning. Doing it online would cost ~30x more and serve no business purpose.

Next steps

More deployment & operations terms

Source & further reading

Primary source: Google Cloud Architecture — MLOps Levels (2023).

Citation policy: this entry is part of the AIDOLS AI Implementation Glossary and may be quoted for research, journalism, and education with attribution to aidolsgroup.com/en/glossary/batch-inference/.