RFC: Integrating KVMem virtual working set for 256K context on 16GB VRAM (Working prototype ready in fork)
Nadie ha tomado este issue todavía.
Evaluación
- Dificultad
- 5/5
- Tiempo estimado
- Más de una semana
- Aptitud para principiantes
- 8/100
- Tipo de issue
- Nueva funcionalidad
- Claridad
- Bastante claro
- Estado de actividad
- Activo
- Stack tecnológico
- cpp
- Área
- machine-learning, performance
Línea de trabajo
This is an RFC, not a scoped task: it asks the maintainer to choose between upstreaming a ~36K LOC KVMem working-set engine and keeping it as a downstream fork, and the 27-comment thread is where that decision is being made. To follow it, read the fork branch beellama-kvmem and the referenced ggml-cuda/gated_delta_net.cu Blackwell fix, then the thread for the maintainer's answer. Done means an architectural decision plus, at most, a targeted PR such as the GDN CUDA fix; nothing here is a first contribution.
Escrito por el modelo de indexación a partir del texto del issue.
Descripción
RFC: Integrating KVMem virtual working set for 256K context on 16GB VRAM (Working prototype ready in fork)
Context & Motivation
Large context windows (128K–256K) on 27B+ models like Qwen3.8-27B (and hybrid architectures with Gated Delta Net) are traditionally difficult to run on consumer hardware (16GB VRAM cards like RTX 4080 / RTX 5060 Ti).
While BeeLlama's native KVarN (and SWA) provides substantial cache savings (~2.67x with kvarn6), pushing beyond 100K–128K on 16GB VRAM still pushes right up against physical memory limits.
We have successfully integrated the KVMem virtual working set engine (arXiv:2609.04852) into BeeLlama v0.4.6, maintaining full compatibility with BeeLlama's core optimizations while allowing true 256K context streaming.
A fully working implementation, benchmarks, and Windows binaries are available in the fork:
👉 Repository & Branch: Andgihat/beellama.cpp (branch: beellama-kvmem)
👉 Release & Binaries: v0.4.6-kvmem
How it works
- Host RAM Virtual Working Set: The complete 262,144 (256K) context lives in pinned Host RAM (DDR5, ~8–12 GB).
- Fixed GPU Slot Pool: Only an active working set (e.g. Budget $B = 36K$ + Reserve $R = 16K$) sits in VRAM (~14.6 GB total with weights, zero OOM).
- Graph Recall & Cache Quantization: Blocks (128 tokens) are staged in/out over PCIe on the fly using Hadamard-rotated quantized slots (
q4_0/q8_0). - Blackwell sm_120 Fix: In the process, we resolved a GDN warp reduction bug in
ggml-cuda/gated_delta_net.cu(lanes_per_colstride and pointer offset checkkeep_rs = K > 1), restoring 100% correct mathematics for hybrid Qwen3.8 on RTX 50-series GPUs.
Benchmark Results (Qwen3.8-27B-UD-Q3_K_XL on RTX 5060 Ti 16GB)
Tested on real text documents from 10K to 256K context:
- Prompt Processing (Prefill @ 10K+ tokens):
915.84 tokens/s(10,196 tokens processed in 11.13s with-b 2048 -ub 1024). - Decode Speed:
35.6 - 40.3 tokens/swith built-in MTP (--spec-type draft-mtp). - MTP Acceptance Rate:
76.0%(consistent 2.46 tokens/round). - RAM Usage @ 10K: Only 187 MB with
q4_0cache. - VRAM Headroom: Fits comfortably within 15.3 GB on a 16GB GPU.
Question for Maintainer (@Anbeeld)
Because the KVMem integration is relatively substantial (~36K LOC including tests, standalone llama-kvmem-server, and runtime adapters), we wanted to check with you first:
- Upstream PR: Would you be interested in having KVMem integrated directly into upstream BeeLlama (e.g. as an optional feature / server target)?
- Specialized Fork: Or would you prefer we maintain this as a specialized downstream fork / companion project (
beellama-kvmem), and only submit targeted PRs (such as the Blackwell GDN CUDA fixes ingated_delta_net.cu) to upstream?
Happy to adapt the changes or submit targeted PRs depending on your architectural preferences. Thank you for the awesome work on BeeLlama!
- Lenguaje dominante
- C++
- Estrellas
- 1.2k
- Forks
- 80
- Merge medio
- 4 d 20 h
- PR fusionados (30 d)
- 2
Preparar el entorno
Este proyecto no incluye contenedor de desarrollo, Dockerfile ni guía de contribución, así que la configuración corre por tu cuenta: empieza por su README y consulta nuestra guía para la primera contribución para los pasos generales.
Primeros pasos
- Lee el issue completo y luego la guía de contribución del proyecto.
- Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
- Haz un fork del repositorio y trabaja en una rama.
- Abre un pull request que haga referencia al número del issue.
Más de Anbeeld/beellama.cpp
-
[BUG] KVarN assertion failure in build_inp_mem_hybrid_iswa() due to uninitialized self_kvarn_rotAbierto
Dificultad 2/5 1-3 horas Aptitud para principiantes 68/100
Anbeeld/beellama.cpp#205 ·
-
Dificultad 3/5 Medio día Aptitud para principiantes 58/100
Anbeeld/beellama.cpp#206 ·
-
Dificultad 3/5 1-2 días Aptitud para principiantes 57/100
Anbeeld/beellama.cpp#204 ·
-
Dificultad 4/5 3-5 días Aptitud para principiantes 45/100
Anbeeld/beellama.cpp#203 · 2 comentarios ·
-
Dificultad 4/5 3-5 días Aptitud para principiantes 45/100
Anbeeld/beellama.cpp#202 · 1 comentario ·
Todos los issues de Anbeeld/beellama.cpp
Issues similares
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 72/100
CachyOS/packageinstaller#144 ·
Los mantenedores suelen responder en 1 día
-
documentation
Dificultad 1/5 Menos de una hora Aptitud para principiantes 82/100
TomerAberbach/profiler-md#951 ·
Los mantenedores suelen responder en 1 día
-
[Bug] Default key routing (JavaStringHash) picks a different partition than the Java client for about half of keysPosiblemente ocupada @0z5a la tomó hoy. Abierto
Dificultad 2/5 1-3 horas Aptitud para principiantes 82/100
apache/pulsar-client-go#1575 ·
Los mantenedores suelen responder en 2 días
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 72/100
pocoproject/poco#5764 ·
Los mantenedores suelen responder en 2 días
-
bug cpp-core-guidelines low-priority
Dificultad 2/5 1-3 horas Aptitud para principiantes 62/100
NatronGitHub/openfx-supportext#164 ·
Los mantenedores suelen responder en 1 día