A proposal on the Hugging Face forums outlines a common GPU execution and memory-management layer designed to decouple application code from specific hardware vendors like NVIDIA, AMD, and Intel. The goal is to allow users to specify a memory budget rather than manually configuring backend-specific flags, device maps, or offloading strategies.
- The runtime would automatically determine layer placement, precision selection (INT4, INT8, FP8), and KV cache management based on available VRAM.
- It introduces a hierarchical memory model with tiers for GPU local VRAM, expansion memory, system RAM, and NVMe storage.
- Low-bit data types are proposed as first-class runtime features to prevent dequantization buffers from defeating quantization benefits.
- The architecture aims to make 13B-class INT4 inference practical on 12 GB consumer GPUs by controlling the entire runtime memory footprint.
This approach seeks to address fragmented software compatibility and VRAM limitations, enabling AI workloads to run efficiently across multi-vendor GPU markets without requiring tight coupling to CUDA or other vendor-specific backends.