Running Low-Latency Analytical Workloads with GPU-Accelerated Presto on NVIDIA GB200 NVL72

· Source: NVIDIA Technical Blog · Field: Technology & Digital — Data Science & Analytics, Cloud Computing & IT Infrastructure, Artificial Intelligence & Machine Learning · Depth: Advanced, medium

Summary

GPU-accelerated Presto, an open-source distributed SQL engine, delivers peak performance and low latency for analytical query workloads by leveraging NVIDIA GPUs. This technology utilizes NVIDIA cuDF algorithms and NVIDIA NVLink for fast GPU-to-GPU communication. Benchmarks on a single-node NVIDIA DGX B200 demonstrated 2.5x to 8.2x faster runtimes for TPC-H-derived datasets (1K and 3K scale factors) compared to 8-10 node Intel Xeon 6642Y CPU clusters. The system also scales out efficiently on multi-node NVIDIA GB200 NVL72 clusters, achieving 64% faster query runtimes through I/O and communication optimizations, including NVIDIA GPUDirect Storage (GDS) and IBM Storage Scale. GDS, which bypasses host CPU and system memory, showed approximately 2x faster runtimes than POSIX cold reads for 10K scale factor datasets on NVL72, making it the preferred approach for performance and cost-efficiency. GPU-accelerated Presto is now available for testing via a technical preview on the IBM watsonx.data platform.

Key takeaway

For Data Engineers or MLOps Engineers deploying large-scale analytical SQL workloads, you should evaluate GPU-accelerated Presto on NVIDIA hardware. This solution offers up to 8x faster query runtimes and 64% overall performance improvements by leveraging NVIDIA cuDF, NVLink, and GPUDirect Storage. Consider testing the technical preview on IBM watsonx.data or exploring the Presto Native "gpu-nightly" Docker image to validate its low-latency and high-throughput capabilities for your production environments.

Key insights

GPU-accelerated Presto delivers substantial latency reduction for analytical workloads through optimized hardware and software integration.

Principles

Method

Benchmarking involved TPC-H derived queries, parquet files, and averaging runtimes; optimizations included GDS, 16 MiB I/O tasks, 16 I/O threads, rebatching, and query rewrites.

In practice

Topics

Code references

Best for: CTO, VP of Engineering/Data, Director of AI/ML, Data Engineer, MLOps Engineer, AI Architect

Related on AIssential

Open in AIssential →

Editorial summary, takeaway, and curation by AIssential. Original article published by NVIDIA Technical Blog.