lm-sys / lm-sys/FastChat

Model Submission: ΩKV Eternal v18.3 KV cache compression

Open
#3,757 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Python
Stars
39.5k
Forks
4.8k
PR merge metrics
No merged PRs in 30d

Description

[ΩKVEternalv18-3.py](https://github.com/user-attachments/files/24126397/KVEternalv18-3.py)

ΩKV Eternal v18.3 memory compression

Supports thousands of racks, billions of users, 100k pages per user. Still fastest compression, no drift. 100% heuristic.

Benchmarks (H200 x8, Llama3-70B, 4M context):
- Ingest: +1.7x throughput
- Query: +1.9-2.1x latency
- Recon error: ≤1e-8 unchanged
- Fidelity: 99.9% (indistinguishable from full KV)
- Verified: Zero regression on BookSum/LongChat/Needle-1M
- Scale: Tested to 1T tokens via distributed sim (Redis + S3); per-user 400M tokens stable (no OOM).
Changelog v18.3 over v18.2:
• Per-user OOM fix: Auto-compress every 1k pages; memmap pages if >500 (Gemini).
• Index locks: ThreadLock on morph/resort; atomic Redis for meta-index.
• No coherence issues: Morph only on idle; queries use snapshot.

## Hosting
- API Type: OpenAI-compatible
- Endpoint: [Grok and Gemini sims]
- Auth: "none"
- Compute Request: [e.g., 8x H100 for testing]

Ready for blind evals—excited to battle!

Ver 18.3 is at bottom in clipboard sized text box

https://grok.com/share/c2hhcmQtMw_00a22053-c0d9-4031-bc6f-26d2e436d0a1

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

Start by reviewing the attached ΩKVEternalv18-3.py file and the linked Grok share, then identify how this submission would connect to FastChat's model serving or evaluation entry points. Verify the stated benchmarks and Redis-based distributed simulation before proposing integration; done should include a reproducible evaluation and a clearly defined FastChat integration path.

Written by the indexing model from the issue text.

Assessment

Tech stack
python, redis
Domain
machine-learning
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
15/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.