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
Related terms
- Online InferenceOnline inference returns model predictions synchronously in response to a live user or system request, within an interactive latency budget.
- Inference CostInference cost is the dollar cost of running a trained AI model in production — per request, per user, or per business outcome — and the operating expense that determines whether an AI feature has positive unit economics at scale.
- Feature StoreA feature store is a centralized data system that stores, versions, serves, and reuses curated machine-learning features — guaranteeing the same feature definitions are used at training time and at online inference time.
- AI PipelineAn AI pipeline is the end-to-end sequence of stages that turns raw data into deployed AI predictions or content — ingestion, cleaning, feature engineering, training, evaluation, deployment, monitoring, and retraining — usually orchestrated as code.
More deployment & operations terms
- Model MonitoringModel monitoring is the continuous measurement of a deployed model's inputs, outputs, and performance signals — including data drift, prediction drift, label drift, latency, and ground-truth accuracy — to detect degradation before it harms business outcomes.
- RAG-as-a-ServiceRAG-as-a-Service is a managed offering that handles document ingestion, chunking, embedding generation, vector storage, retrieval, and LLM grounding behind a single API — letting teams ship retrieval-augmented features without building the underlying pipeline.
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/.