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.
Glossary
MLPerf

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.
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.
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.
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.
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.
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.
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.
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.
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.
Enabling Efficiency, Speed & Accuracy
Intelligent Analysis, Decision & Execution
We build AI systems for teams that need search across company data, workflow automation across tools, or AI features inside products and internal software.
Talk to Us
Search across company data
Give teams answers from docs, tickets, runbooks, and product data with sources and permissions.
Useful when people spend too long searching or get different answers from different systems.

Automate internal workflows
Use AI to route work, draft outputs, trigger actions, and keep approvals and logs in place.
Useful when repetitive work moves across multiple tools and teams.

Add AI to products and internal tools
Build assistants, guided actions, or decision support into the software your team or customers already use.
Useful when AI needs to be part of the product, not a separate tool.
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.
Related Terms
Understanding MLPerf requires familiarity with the hardware, software, and networking components that directly influence benchmark results.
CUDA
The foundational parallel computing platform for NVIDIA GPUs. MLPerf submissions are heavily optimized using CUDA libraries like cuBLAS and cuDNN to achieve peak performance. Without a mature CUDA implementation, a hardware platform cannot be competitive in the training benchmarks.
TensorRT
An inference optimization SDK from NVIDIA. It performs graph optimizations, layer fusion, and precision calibration (FP8/INT8) to maximize throughput. MLPerf Inference submissions frequently use TensorRT to achieve state-of-the-art latency and throughput on the datacenter and edge categories.
NCCL
The NVIDIA Collective Communications Library provides high-performance primitives like all-reduce and all-gather. In MLPerf Training, scaling to thousands of GPUs requires NCCL to efficiently synchronize gradients across nodes without becoming a bottleneck.
HBM3e
The latest high-bandwidth memory standard. MLPerf benchmarks like GPT-3 training are extremely memory-bandwidth bound. HBM3e provides the terabytes-per-second of memory bandwidth necessary to keep thousands of compute cores fed with data, directly impacting time-to-train metrics.
InfiniBand
A high-performance interconnect used in large-scale clusters. For MLPerf submissions involving hundreds or thousands of nodes, InfiniBand's RDMA capability provides the low-latency, high-bandwidth fabric required to prevent networking from becoming the scaling bottleneck during distributed training.
GPU Direct Storage
Enables a direct data path from NVMe storage to GPU memory. In MLPerf benchmarks with massive datasets, this bypasses the CPU and system memory, significantly accelerating I/O and ensuring GPUs do not stall waiting for the next batch of training data.

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.
Partnered with leading AI, data, and software stack.
How We Work
Custom AI workflows for your Business
One-fit-all AI don't work for modern businesses. At Inferensys, we aim to understand your business & custom requirements; which we use to define most efficient agentic workflows, the data, and the tools for your business.
01
Review the use case
We understand the task, the users, and where AI can actually help.
Read more02
Pick the right approach
We define what needs search, automation, or product integration.
Read more03
Build the first useful version
We implement the part that proves the value first.
Read more04
Improve from there
We add the checks and visibility needed to keep it useful.
Read moreThe first call is a practical review of your use case and the right next step.
Talk to Us