NVIDIA Vera Storage Benchmarks: Faster Encryption, Compression, Integrity Checking, and Recovery for AI-Native Storage
https://developer.nvidia.com/blog/nvidia-vera-storage-benchmarks-faster-encryption-compression-integrity-checking-and-recovery-for-ai-native-storage/📌 【NVIDIA 技術解析】解決 AI 時代的儲存瓶頸:Vera 如何加速 Agentic AI 的資料處理
TL;DR:NVIDIA Vera 透過專為儲存設計的架構,在加密、壓縮與完整性檢查等任務上超越 x86 CPU。
🎣 當 AI Agent 變多,儲存系統成為效能殺手
在 Agentic AI(代理型 AI)的工作流程中,儲存不再只是靜態的資料庫。當 AI Agent 在檢索企業知識、存取持久記憶、重複使用 KV cache(鍵值快取)或執行工具時,儲存系統必須持續供應並保護這些驅動推理迴圈的資料。
隨著 Agent 的併發量(Concurrency)與 Context Window(上下文視窗)規模不斷擴大,每一次 Agent 步驟都可能觸發多次儲存操作。這些操作包含加密、壓縮、計算校驗碼(Checksums)與冗餘計算(Redundancy)等。若這些處理過程落在 CPU 處理路徑中,處理速度若跟不上 SSD 或網路的速度,就會成為整個加速運算架構的效能瓶頸。
🧩 Vera 架構:為 AI 工廠打造的儲存處理核心
為了縮小「儲存處理差距」,NVIDIA 在 BlueField-4 STX 儲存處理器中引入了 Vera CPU。這款架構不僅是為了餵飽 Rubin GPU 而設計,也同時加速了 CPU 端的儲存處理任務。
Vera CPU 的技術規格包含:
- 核心設計:擁有 88 個 NVIDIA 自研的 Olympus CPU 核心,完全相容於 Armv9.2 指令集,並支援 176 個 Spatial Multithreading 執行緒。
- 高速傳輸:採用 NVIDIA Scalable Coherency Fabric (SCF),提供高達 3.4 TB/s 的雙向頻寬(Bisection Bandwidth)與 164 MB 的統一 L3 快取。
- 記憶體子系統:配備 SOCAMM2 LPDDR5X 記憶體,提供高達 1.2 TB/s 的總體記憶體頻寬,確保在高併發工作負載下,核心仍能獲得穩定的資料供應。
📊 基準測試結果:Vera 在關鍵儲存原語中全面超越 x86
透過對比常見的軟體函式庫(如 OpenSSL、Zstandard、LZ4),NVIDIA 在隔離單一處理任務的微基準測試(Microbenchmarks)中發現,Vera 在多項關鍵指標上表現優於傳統 x86 CPU:
- 安全性與完整性:在加密(Encryption)、解密(Decryption)以及完整性檢查(Integrity Checking)方面表現更佳。
- 資料效率:在壓縮(Compression)與解壓縮(Decompression)任務上擁有更高的吞吐量。
- 復原能力:在資料復原(Recovery)與奇偶校驗(Parity)計算上展現更強效能。
- 多階段管線:在多階段儲存管線(Multi-stage storage pipeline)的測試中,Vera 能同時處理更多併發資料流,且不會導致 CPU 資源、功耗或散熱需求成比例增加。
💡 深入分析:解決「單核效能」與「頻寬需求」的雙重挑戰
儲存處理任務對 CPU 有兩種截然不同的需求:
- 單核持續效能:在單一資料流中,加密與壓縮必須快速完成,才能進入下一階段處理,這需要強大的單核指令吞吐量。
- 高頻寬與低延遲:在系統層級,這些操作需要跨越大量併發流,對記憶體頻寬與可預測的延遲要求極高。
Vera 的 Olympus 核心結合了寬指令吞吐量、先進分支預測、深層亂序執行(Out-of-order execution)以及向量與加密資源,成功同時滿足了這兩項需求,讓儲存軟體在處理高吞吐量資料流時,能保有更多的 CPU 餘裕(Headroom)。
🎯 實務啟示
對於建構 AI 原生資料平臺的工程師而言,這意味著:
- 降低基礎設施成本:透過更高的壓縮吞吐量,可以減少儲存容量與頻寬需求。
- 提升系統韌性:更快的加密與完整性檢查,能在不犧牲效能的前提下,強化 AI 系統的安全性與資料保護。
- 消除效能瓶頸:使用專為加速運算設計的處理器,可以確保儲存處理速度能跟上高速 SSD 與網路,避免資料流停滯。
🔗 來源
- 標題:NVIDIA Vera Storage Benchmarks: Faster Encryption, Compression, Integrity Checking, and Recovery for AI-Native Storage
- 作者/機構:Elizabeth Goodman @ NVIDIA Developer
- 連結:https://developer.nvidia.com/blog/nvidia-vera-storage-benchmarks-faster-encryption-compression-integrity-checking-and-recovery-for-ai-native-storage/
#NVIDIA #Vera #BlueField4 #AIInfrastructure #Storage #Armv9 #DataCenter #AgenticAI #CloudComputing #HardwareAcceleration
原始資料 NVIDIA Developer · 收集於 2026-08-04
摘要原文
Storage is an active part of every agentic AI workflow. As agents retrieve enterprise knowledge, access persistent memory, reuse key-value (KV) cache data, execute tools, and generate new results, storage systems must continuously supply and preserve the data that moves the agent reasoning loop. Each agent step can trigger multiple storage operations, and those operations can repeat across thousands of concurrent agents with increasingly larger context windows. Supplying and preserving this data requires more than basic reads and writes. AI inference runs on GPUs, but agentic processes, tool calls, data management tasks, and the storage services that support them run on CPUs. During writes, storage may compress and encrypt data, calculate checksums, and calculate redundancy. During reads, it may validate, decrypt, decompress, or reconstruct data before returning it to the application. These functions are essential to the security and resilience of AI systems. Each function also requires additional CPU processing as data moves through the storage path. As agent concurrency (multiple users, AI agents, or tasks running in parallel) and context volumes grow, storage must perform more of this work without constraining application responsiveness or token generation; it must supply data at the rate required for accelerated computing. Many of these functions sit directly in the data path; one delayed operation can slow the broader data flow. Scaling them with conventional CPUs can require more cores, power, and cooling, increasing infrastructure cost while still leaving performance dependent on the slowest step. Faster SSDs and networks cannot deliver their full potential if the processor securing, protecting, and preparing the data cannot keep pace. Closing the storage processing gap The NVIDIA Vera BlueField-4 STX Storage Processor , a key component of the NVIDIA STX foundation for AI-native data platforms, brings the NVIDIA Vera CPU performance directly into the storage data path. The same Vera CPU architecture designed to keep NVIDIA Rubin GPUs fed also accelerates the CPU-side storage processing. The benchmark results show Vera outperforming the x86 CPU across encryption and decryption, recovery, integrity checking, compression and decompression, and a multi-stage storage pipeline. These gains enable storage platforms to process more data and apply essential enterprise services with less CPU and power overhead, while higher compression throughput helps reduce storage capacity and bandwidth demands. This post explains how the Vera CPU in BlueField-4 STX accelerates the storage processing required by agentic AI, helping AI-native storage platforms secure, protect, validate, and compress more data while increasing storage-processing throughput and efficiency. Vera CPU architecture: Built for storage’s dual demands Vera CPU includes 88 NVIDIA-designed Olympus CPU cores that are fully compatible with the Armv9.2 instruction set. The CPU supports 176 NVIDIA Spatial Multithreading threads. It pairs these cores with the NVIDIA Scalable Coherency Fabric (SCF), Small Outline Compression Attached Memory Module (SOCAMM2) LPDDR5X memory to sustain strong single-thread performance, and high-throughput CPU execution at AI-factory scale. The SCF provides a coherent, on-die data path across the cores, shared cache, memory controllers, and I/O, with up to 3.4 TB/s of bisection bandwidth and a 164 MB unified L3 cache. This gives active cores high-bandwidth, predictable access to shared data as workloads scale across the processor. The SOCAMM2 LPDDR5X memory subsystem complements the fabric with up to 1.2 TB/s of aggregate memory bandwidth, or up to 14 GB/s per core, helping keep the NVIDIA Olympus cores supplied across bandwidth-intensive and highly concurrent workloads. Modular, field-replaceable memory combines LPDDR5X power efficiency with the serviceability and reliability required for datacenter infrastructure. Storage primitives place two distinct demands on a CPU. First, within each data stream, encryption, integrity checking, recovery, compression, and decompression must complete quickly before subsequent storage processing can proceed, making sustained per-core performance important. Second, across the system, these operations run over many concurrent streams and repeatedly move data through caches and memory, making bandwidth and predictable latency equally important. Vera addresses both requirements. The Olympus core combines wide instruction throughput, advanced branch prediction, deep out-of-order execution, and vector and cryptographic resources to help each core sustain instruction throughput across control-heavy and data-processing code. NVIDIA Spatial Multithreading, the monolithic compute die, SCF, unified L3 cache, and high-bandwidth SOCAMM2 memory help keep active cores supplied with data while reducing thread-to-thread interference and supporting more predictable data access under load. Together, these capabilities help explain the measured gains across encryption, integrity checking, parity calculations, compression, and the multi-stage storage pipeline. This enables the BlueField-4 STX Storage Processor to sustain more CPU-side storage processing across concurrent data streams without proportional increases in CPU resources, power, and cooling. Measuring foundational storage performance Storage tasks execute repeatedly across storage read, write, and recovery paths. Their throughput and efficiency help determine whether CPU-side processing keeps pace with SSDs and networks or becomes the limiting stage in the data path. The storage primitive microbenchmarks in this post isolate these functions to measure the processor’s contribution. They show the CPU performance and headroom available in Vera for building higher-throughput, more efficient storage services. Each test runs within a single process using data already held in memory. The tests exclude file I/O, disk performance, networking, command startup, and external-device bottlenecks unless otherwise identified. The benchmark set uses common libraries, including OpenSSL, Zstandard, and LZ4, along with comparable implementations optimized to use the native instructions available on Arm and x86 processors. A purpose-built test framework runs each workload consistently and controls buffer sizes, thread counts, CPU placement, timing, correctness validation, and result collection. The algorithms and many of the software implementations are widely adopted. The test framework applies the same workload definitions and controls across Vera and x86, enabling a consistent processor comparison. The results can be reproduced using the source code, scripts, fixed software versions, configurations, and result files, although the complete benchmark set is not an off-the-shelf public benchmark. These measurements establish Vera’s performance on the storage building blocks that influence secure data movement, resilience, capacity efficiency, and service density. Production storage paths often apply several of these operations to the same data, causing their CPU-processing requirements to accumulate. When combined in production storage software, the performance of these individual operations contributes to aggregate throughput and CPU efficiency. Higher throughput across individual primitives and the multi-stage pipeline gives storage software more CPU headroom to keep pace with SSDs and networks, support concurrent data flows, and apply essential data services efficiently. End-to-end testing is still required to quantify complete storage-system or GPU-performance outcomes. Securing more AI data with faster encryption AI factories process sensitive information, including model assets, enterprise knowledge, agent context, prompts, outputs, and customer data. AES-128 is widely used for data-at-rest and data-in-flight encryption.
由 tencent/hy3:free 自動生成