Inferensys

Glossary

MLPerf

An industry-standard benchmark suite for measuring the performance of machine learning hardware, software, and cloud platforms across a range of training and inference tasks.
ML engineer managing model training cluster on laptop, GPU utilization visible, technical deep learning setup.
BENCHMARKING SUITE

What is MLPerf?

MLPerf is the industry-standard benchmark suite for measuring the performance of machine learning hardware, software, and cloud platforms across a range of training and inference tasks.

MLPerf is a comprehensive, vendor-neutral benchmarking suite developed by the MLCommons consortium to provide standardized, reproducible performance measurements for machine learning training and inference. It spans diverse workloads, including image classification, object detection, natural language processing, and reinforcement learning, enabling direct comparisons between competing hardware accelerators like GPUs, TPUs, and custom ASICs.

The benchmark is divided into closed and open divisions; the closed division mandates identical model architectures and hyperparameters for strict hardware comparison, while the open division allows arbitrary optimizations. Results are submitted and peer-reviewed, providing procurement leads and infrastructure architects with transparent, real-world metrics like throughput and latency to guide on-premises GPU cluster investment decisions.

BENCHMARK ARCHITECTURE

Key Features of MLPerf

MLPerf is a consortium-driven benchmark suite that provides standardized, peer-reviewed metrics for comparing the performance of AI hardware, software, and cloud platforms. It covers both training and inference across diverse workloads.

01

Closed Division: Apples-to-Apples Comparison

The Closed Division mandates the use of a mathematically equivalent model and optimizer to ensure direct hardware and software system comparisons. Submitters must use the reference implementation, such as a specific ResNet-50 or BERT variant, preventing accuracy-advantageous cheating. This division isolates the raw throughput and latency capabilities of the underlying infrastructure, making it the primary metric for hardware procurement decisions.

Identical Math
Model Equivalence
02

Open Division: Innovation Showcase

The Open Division allows unrestricted model architecture, learning rate schedules, and optimization techniques to push the absolute boundaries of speed. While not directly comparable between vendors, this division drives industry innovation by rewarding novel approaches like advanced pruning, neural architecture search, or low-precision arithmetic that achieve state-of-the-art training times or inference latency.

Unrestricted
Model Design
03

Training Benchmarks: Time-to-Model

Training benchmarks measure the wall-clock time required to train a model to a target quality threshold. Key workloads include:

  • Image Classification: ResNet-50 on ImageNet
  • NLP: BERT on Wikipedia/BooksCorpus
  • Recommendation: DLRM on Criteo Terabyte
  • Reinforcement Learning: Mini-go
  • Scientific: CosmoFlow These tests stress GPU interconnect bandwidth and all-reduce collective operations.
Minutes
Target Metric
04

Inference Benchmarks: Queries Per Second

Inference benchmarks evaluate a system's ability to process prediction requests under strict latency constraints. The suite is split into two scenarios:

  • Server Scenario: Maximizes throughput under a target latency budget (e.g., 99th percentile < 15ms), simulating cloud API backends.
  • Offline Scenario: Maximizes throughput with no latency constraint, simulating batch processing. Workloads span vision, speech, and medical imaging.
Server & Offline
Scenarios
05

Power Measurement: Efficiency Metrics

The optional Power Division adds energy efficiency to the benchmark, measuring performance per watt. Systems are instrumented with precision power meters at the power supply unit or bus level. This metric is critical for large-scale AI factory deployments where operational expenditure is dominated by electricity costs and thermal management. It penalizes brute-force scaling in favor of performance-per-watt optimization.

Watts
Measurement Unit
06

Governance & Peer Review

MLPerf is governed by the MLCommons consortium, an open engineering group with members from academia and industry. Every submission undergoes a rigorous peer-review process where results are reproduced and validated by third parties. This prevents benchmark gaming and ensures that published numbers—whether for a single NVIDIA H100 or a 10,000-node cluster—are verifiable and trustworthy for enterprise procurement.

Peer-Reviewed
Validation
MLPERF BENCHMARKING

Frequently Asked Questions

Clear, technical answers to the most common questions about the MLPerf benchmark suite, its methodology, and its role in evaluating AI infrastructure performance.

MLPerf is an industry-standard benchmark suite developed by the MLCommons consortium for measuring the performance of machine learning hardware, software, and cloud platforms. It works by defining a set of representative ML tasks with fixed model architectures, datasets, and quality targets. Submitters run these workloads on their systems and report the time to train a model to a specified quality threshold or the throughput and latency of serving inference requests. Results are peer-reviewed and published in a transparent, apples-to-apples format. The suite is divided into two primary tracks: MLPerf Training, which measures the wall-clock time to train models like BERT, ResNet, and GPT-3 to a target metric, and MLPerf Inference, which evaluates serving performance across scenarios including single-stream, multi-stream, server, and offline processing. A third track, MLPerf Tiny, targets ultra-low-power microcontrollers and embedded devices. By standardizing the software stack and quality bars, MLPerf isolates hardware and system-level performance, making it the de facto standard for procurement decisions in AI infrastructure.

Prasad Kumkar

About the author

Prasad Kumkar

CEO & MD, Inference Systems

Prasad Kumkar is the CEO & MD of Inference Systems and writes about AI systems architecture, LLM infrastructure, model serving, evaluation, and production deployment. Over 5+ years, he has worked across computer vision models, L5 autonomous vehicle systems, and LLM research, with a focus on taking complex AI ideas into real-world engineering systems.

His work and writing cover AI systems, large language models, AI agents, multimodal systems, autonomous systems, inference optimization, RAG, evaluation, and production AI engineering.