[ENHANCEMENT] Query-Aware Cache Selection for Efficient LLM Serving

Abierto
#65 0 comentarios 0 reacciones 0 asignados Ver en GitHub

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
Stack tecnológico
python, pytorch

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
  1. Implement a query profiler module (<1ms overhead).
  2. Add a policy manager to select caching strategies on the fly.
  3. Integrate with existing cache storage and serving scheduler.
  4. 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

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de volcengine/veScale

Todos los issues de volcengine/veScale

Issues similares

Más issues de Python

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.