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

オープン
#65 コメント 0 件 リアクション 0 件 担当者 0 名 GitHub で見る

まだ誰も着手していません。

評価

難易度
5/5
見積もり時間
1週間以上
初心者へのやさしさ
8/100
issue の種類
機能追加
明瞭さ
説明が足りない
活発さ
停滞
技術スタック
python, pytorch

調査の方向性

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.

索引モデルが issue の本文から書いたものです。

説明

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.
主要言語
Python
スター
1k
フォーク
65
平均マージ
21時間 34分
マージ済み PR(30日)
1

環境構築

はじめの一歩

  1. issue を最後まで読み、次にプロジェクトのコントリビューションガイドを読みます。
  2. 着手することを issue にコメントします — 二人が同じ作業をするのを防げます。
  3. リポジトリをフォークし、ブランチを切って変更します。
  4. issue 番号を参照したプルリクエストを送ります。

volcengine/veScale のほかの issue

volcengine/veScale の issue をすべて見る

似ている issue

Python の issue をもっと見る

新しい issue をメールで受け取る

初心者向けの GitHub issue を短くまとめたダイジェスト。