microsoft / microsoft/MInference

[Question]: Feasibility of evaluating complex KV compression methods via single-turn or batch-input modes

Open
#200 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

question
Dominant language
Python
Stars
1.2k
Forks
82
Avg merge
1d 18h
Merged PRs (30d)
1

Description

Describe the issue

Thank you for your inspiring work on SCBench!

I am currently interested in benchmarking several SOTA KV cache compression algorithms (such as ShadowKV, OmniKV, etc.) using SCBench. However, integrating these methods into the SCBench framework is proving to be quite challenging. Due to the complexity of their original implementations, modifying their codebases to fully support the specific multi-turn / shared-context mechanisms defined in SCBench involves significantly high engineering costs.

Questions Given these implementation constraints, I would like to ask for your advice on the validity of the following alternative evaluation strategies:

Single-turn Evaluation: Is it reasonable to utilize SCBench solely for single-turn evaluation (i.e., treating the first turn as the primary metric)? I understand that the core contribution of SCBench is analyzing the full lifecycle (especially cache reuse), but I am wondering if the dataset itself still holds value for validating compression quality in a single-turn setup compared to other benchmarks like LongBench or InfiniteBench.

One-pass / Batch Evaluation: Would it be methodologically sound to concatenate the context with all the questions (e.g., Context + Q1 + Q2 + Q3...) into a single prompt and have the model generate all answers in one pass?

Any insights or suggestions would be greatly appreciated.

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

The issue names no files, tests, or entry points to begin with. Start by identifying SCBench's evaluation entry points and documentation for multi-turn and shared-context modes, then determine whether the requested single-turn or batch strategies are supported and document the maintainer's guidance.

Written by the indexing model from the issue text.

Assessment

Tech stack
python
Domain
machine-learning, testing-qa
Issue type
Documentation
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
20/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.