Skip to content
aiqbench takeAI Products

aiqbench analysis

This presentation details how the open-source Vortex file format eliminates data loading bottlenecks by enabling zero-copy pipelines that stream S3 storage directly to GPUs at speeds up to 60 Gbps. By utilizing cascading lightweight encodings and layout-based segment pruning, the technology removes the need for upfront data reprocessing, significantly accelerating ML training workflows.
Source coveringInfoQ
What this isA model's reading of the article and related coverage, written for aiqbench. Not the publisher's words.

Presentation: From S3 to GPU in One Copy: Rethinking Data Loading for ML Training

InfoQ40 min read

Onur Satici explains how Vortex, an open-source columnar file format under the Linux Foundation, revolutionizes high-throughput data loading. He details how cascading lightweight encodings, layout-based segment pruning, and zero-copy memory pipelines eliminate CPU/NVMe bottlenecks to stream S3 data straight to GPUs at speeds up to 60 Gbps without requiring upfront data reprocessing. By Onur Satici

Onur Satici: Before I get into anything, I want to show you this video. Not specifically like what's playing in the video, but how we produce this video. Because this is not backed by a regular MP4 file in some main disk, but this is actually a visualization of a file scan. What I mean by this is we have a Vortex file, Vortex being a columnar file format. It has three columns, one per color. Each column would then have a row per frame of this video. Each frame would include around 8 million pixels, because it's a 4K video. Then we then process this data, which is three columns, around 8 million pixels per frame, 60 frames per second, so around 13 gigabits per second, from S3, through the network card, over the CPU, and to the GPU. The GPU is seeing this data this fast, but we want to see what's happening in the GPU, we want to visualize that. We can't downlink that much data to our laptops, so because it's already in the GPU, I'm using the GPU itself to re-encode it into H.264, wrap it into TCP buffers, send it over my SSH tunnel,…

Excerpt shown under the publisher's RSS terms · 200 words · full text and figures are on the publisher's site

Related coverage