Storage Acceleration (KV Cache Tiering)
FX series all-flash NVMe-oF arrays plus a KV-cache tiering software stack: signed benchmarks on a 480B model in production deployment form show throughput +29–40% and TTFT −26–32%.
Core Capabilities and Measured Basis
- More verifiable output for the same GPU budget: storage spend within ~10% of GPU cost (joint-test basis) for a 29–40% throughput gain (measured, R2/R3)
- Long-context cold recovery (agent / code-assistant session-recovery storms): 8.6–20× faster than no-external-storage re-compute (measured, R2)
- fs:// shared pool verified for cross-instance hot sharing; two independent runs within 5% deviation (measured, R3)
- Existing clusters need not add GPUs first: model loading 6.2–9.3× faster under NFS bottlenecks (measured, R9, Ascend platform)
Supporting Evidence
LMCache parallel-read patch, multi-GPU KV tiering scale-out, concurrent model loading, model-switch effective TPS, training checkpoint concurrent writes (Qwen2.5-32B/7B).
Download report PDF ↓Qwen3-Coder-480B-FP8, single 8-GPU instance (TP=8 standard production topology), long-context cold recovery, three-way comparison across concurrency levels.
Download report PDF ↓Dual 4-GPU instances, nine load levels, full metrics (TTFT p50/p90/p99, TPOT, throughput, disk bandwidth); fs:// shared-pool cross-instance hot sharing verified; two independent runs within 5% deviation.
Download report PDF ↓Official compilation of R2 + R3 issued by a third-party testing organization.
Download report PDF ↓Huawei Atlas 910B ×8 (Kunpeng-920): model-serving load (DeepSeek-32B/70B), training weight/checkpoint I/O (Qwen-7B), training-data acceleration (YOLOv8/COCO) — three groups against an NFS baseline (Ascend platform, labeled as such; contact us for access).
Contact us for access →The Engagement Path
Joint test first, decisions second: gate-based acceptance with built-in stop-loss. The full costing model is provided as reproducible Python after NDA — customers can rerun it with their own parameters. Every key figure on this site carries a report ID and is open to third-party verification.