NVIDIA's AIStore Stops GPU Clusters From Starving on Slow Data
NVIDIA's open-source AIStore hits v4.7 with a production-hardened Get-Batch API, TAR shard indexing, and S3-compatible distributed object storage built for petascale ML training.
PRO- v4.7 released: Small stability patch fixing IC notification metadata growth, adding Go runtime Prometheus metrics, and tightening downloader egress security.
- Get-Batch API hardened: Recent v4.5/4.6 releases overhauled the ML batch retrieval API to fix work-item leaks, bound abort latency, and handle slow/disconnecting clients under heavy load.
- TAR shard index (v4.5): New indexed extraction from TAR archives lets GET and Get-Batch skip full archive scans, persisted in a dedicated system bucket.
- Free and open-source: MIT-licensed, runs on commodity Linux hardware with no special dependencies; deployable from a single VM to petascale Kubernetes clusters.
- S3-compatible + multi-cloud: Drop-in S3 API, native backends for AWS, GCS, Azure, and OCI, with PyTorch and boto3 integrations included.
- ETL offload built-in: Run data transformations inline (per-read) or offline (batch) directly on storage nodes, close to the data, without moving it first.
AIStore (AIS) is NVIDIA's open-source, MIT-licensed distributed object storage system built from the ground up for AI workloads. It has been quietly maturing since 2017, and the recent v4.7 patch release caps a rapid series of major updates that have fundamentally reshaped how large-scale ML training pipelines can interact with storage. If your GPU cluster has ever sat idle waiting on data, this project is worth a serious look.
The Problem It's Solving
As AI and HPC datasets continue to increase in size, the time spent loading data begins to place a strain on total application performance. Fast GPUs are increasingly starved by slow I/O. The standard fix is to throw more workers at the DataLoader, but that only goes so far when the bottleneck is the storage layer itself. Traditional storage systems often cannot provide sufficient throughput for modern AI training workloads. Large language models may require 10+ GB/s sustained read performance, while computer vision training can demand even higher throughput for image and video data.
AIStore's answer is to treat storage as a first-class participant in the training pipeline, not just a dumb file server. AIS is a lightweight distributed storage stack tailored for AI applications. It's an elastic cluster that can grow and shrink at runtime and can be deployed anywhere from a single Linux machine to a bare-metal cluster of any size. Built from scratch, it provides linear scale-out, consistent performance, and a flexible deployment model.
What Makes It Different
AIS is a reliable storage cluster that can natively operate on both in-cluster and remote data, without treating either as a cache. It consistently shows balanced I/O distribution and linear scalability across an arbitrary number of clustered nodes. That last point matters: most distributed storage systems hit coordination bottlenecks as you add nodes. AIS is designed so that adding a node adds proportional throughput.
The feature set is dense. Here are the highlights most relevant to ML teams:
- Get-Batch API: A high-performance API for retrieving multiple objects and/or archived files in a single request. Behind the scenes, Get-Batch assembles the requested data from across the cluster and delivers the result as a continuous serialized stream. Regardless of retrieval source, Get-Batch always preserves the exact ordering of request entries in both streaming and buffered modes. This is huge for training pipelines that need deterministic batch ordering.
This story is for Pro members
You've reached the end of the free preview. Upgrade to AlphaSignal Pro to read the full article - and everything else behind the paywall.