[ENHANCEMENT] Query-Aware Cache Selection for Efficient LLM Serving
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
- Necesita aclaración
- Estado de actividad
- Estancado
- Área
- machine-learning, performance
Línea de trabajo
This is a design proposal rather than a scoped task: it sketches a query-aware caching layer (profiler, policy manager, scheduler integration) for LLM serving, and the payload names no file, module or test in veScale. A newcomer would first have to confirm whether veScale, a PyTorch training framework, even contains the serving scheduler and cache storage the proposal assumes, and whether the referenced TinyServe paper is meant to be ported. Done would mean an agreed design with maintainers before any code; with no comments or assignee after 456 days, that conversation has not started.
Escrito por el modelo de indexación a partir del texto del issue.
Descripción
Problem Description
I would like to enhance the cache mechanism for LLM serving in Volcengine. The goal is to make the cache usage more adaptive to heterogeneous query workloads by dynamically adjusting reuse strategies.
Proposed Solution
The proposed enhancement is a Query-Aware Cache Selection (QACS) mechanism:
- Lightweight Query Profiling: Efficiently estimate query complexity (length, entropy, semantic redundancy).
- Dynamic Cache Selection: Adaptively choose between aggressive reuse, partial reuse, or fresh recomputation.
- Policy Control: Expose configurable knobs (
reuse_ratio,cache_budget,latency_accuracy_tradeoff) for fine-grained control. - Scheduler Integration: Integrate into the Volcengine serving scheduler for runtime-aware resource allocation.
Alternatives Considered
- Uniform cache reuse across all queries, which is simple but cannot adapt to different workloads.
- Manual configuration at deployment time, which lacks flexibility and incurs higher operational overhead.
The proposed TinyServe provides adaptive, per-query cache control without requiring manual tuning.
Implementation Plan
- Implement a query profiler module (<1ms overhead).
- Add a policy manager to select caching strategies on the fly.
- Integrate with existing cache storage and serving scheduler.
- Provide developer-facing APIs for configuration.
Additional Context
- This enhancement has been validated at scale across multiple LLMs, consistently improving efficiency and robustness.
- Reference: Dong Liu et al., “TinyServe: Query-Aware Cache Selection for Efficient LLM Serving,” ACM Multimedia 2025 (Oral).
- Expected benefits:
- ⚡ Efficiency: Up to 3x latency reduction under mixed workloads.
- 🎯 Quality: Maintains high generation quality even with aggressive cache usage.
- 📈 Scalability: Supports larger models within the same GPU budget.
- Lenguaje dominante
- Python
- Estrellas
- 1k
- Forks
- 65
- Merge medio
- 21 h 34 min
- PR fusionados (30 d)
- 1
Preparar el entorno
- Incluye un Dockerfile o un archivo de Docker Compose
- Sin plantilla de pull request
- Leer la guía de contribución
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 volcengine/veScale
-
Dificultad 1/5 Menos de una hora Aptitud para principiantes 12/100
volcengine/veScale#75 ·
-
Dificultad 5/5 Más de una semana Aptitud para principiantes 10/100
volcengine/veScale#73 · 1 comentario · 3 reacciones ·
-
Dificultad 5/5 Más de una semana Aptitud para principiantes 8/100
volcengine/veScale#72 · 5 reacciones ·
-
Dificultad 3/5 1-2 días Aptitud para principiantes 30/100
volcengine/veScale#68 ·
-
Dificultad 3/5 1-2 días Aptitud para principiantes 12/100
volcengine/veScale#63 ·
Todos los issues de volcengine/veScale
Issues similares
-
bug
Dificultad 2/5 1-3 horas Aptitud para principiantes 78/100
Los mantenedores suelen responder en 1 día
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 66/100
Los mantenedores suelen responder en 1 día
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 75/100
docling-project/docling-pipelines#669 ·
Los mantenedores suelen responder en 1 día
-
blocked kind/enhancement
Dificultad 2/5 1-3 horas Aptitud para principiantes 78/100
opendatahub-io/agent-eval-harness#329 · 2 comentarios · 1 reacción ·
-
cc_wrapper crashes with ValueError on Windows when a path is on another drivePosiblemente ocupada @TrapsterDK la tomó hoy. Abierto
Dificultad 2/5 1-3 horas Aptitud para principiantes 79/100
tweag/rules_haskell#2492 ·
Los mantenedores suelen responder en 1 día