Photo by phyo min on Unsplash. Source: https://unsplash.com/photos/KypgZEAIuio (Unsplash License).

IBM, NVIDIA and Supermicro packaged a shared KV cache tier this week, and their own documentation names the limit. It is the network, not the storage.

  • Cached context sits on an all-flash tier running IBM Storage Scale, moved by NVIDIA Dynamo over Spectrum-X Ethernet.
  • The 56x time to first token figure comes from an IBM Redbooks architecture published in June, not a November benchmark.
  • Across 200 requests the cache took throughput from 0.19 to 4.26 requests per second, a 22x improvement.
  • With four clients pushing 200 GB/s of competing traffic it held 3.6 requests per second, still 18x faster than recomputing.
  • The Redbook states that the storage tier has headroom it cannot deliver, and that more 400GbE client-side links would unlock it.
  • Ask for bandwidth per GPU node, not the multiplier, when you size the design.

Read the full analysis.

By Ivan Tarin

Ivan Tarin is a Principal Product Marketing Manager at SUSE, where he owns go-to-market strategy and positioning for a seven-product cloud-native portfolio spanning Kubernetes, virtualization, storage, security, and observability. A former full-stack developer who shipped production code for enterprise and public-sector clients including U.S. national laboratories, Ivan translates complex infrastructure and AI technology into messaging that lands with developers, platform teams, and enterprise buyers. He has presented at KubeCon, SUSECON, and AWS Developer Week, and is currently pursuing an MS in Artificial Intelligence at the University of Colorado Boulder.

Leave a Reply

Your email address will not be published. Required fields are marked *

Get the next one before it is old news

Independent analysis of cloud-native infrastructure, Kubernetes and data center economics. No vendor spin.