Kuntai Du (@this_will_echo) profile picture

Chief Scientist | Committer of vLLM / LMCache / Production Stack

Joined January 2022
Photo by Kuntai Du (@this_will_echo)Photo by Kuntai Du (@this_will_echo)Photo by Kuntai Du (@this_will_echo)Photo by Kuntai Du (@this_will_echo)Photo by Kuntai Du (@this_will_echo)Photo by Kuntai Du (@this_will_echo)Photo by Kuntai Du (@this_will_echo)Photo by Kuntai Du (@this_will_echo)Photo by Kuntai Du (@this_will_echo)Photo by Kuntai Du (@this_will_echo)
Kuntai Du retweeted
Today weโ€™ve announced to the world that ๐“๐ž๐ง๐ฌ๐จ๐ซ๐ฆ๐ž๐ฌ๐ก ๐๐ฅ๐š๐ญ๐Ÿ๐จ๐ซ๐ฆ, the ๐ฆ๐š๐ง๐š๐ ๐ž๐ฆ๐ž๐ง๐ญ ๐ฅ๐š๐ฒ๐ž๐ซ ๐Ÿ๐จ๐ซ ๐€๐ˆ ๐ข๐ง๐Ÿ๐ž๐ซ๐ž๐ง๐œ๐ž ๐๐š๐ญ๐š, is officially live and enterprise-ready ๐Ÿš€ Read the full announcement ๐Ÿ‘‡ na2.hubs.ly/H08nsMN0
4
1
12
279
Kuntai Du retweeted
Day 1 of The AI Conference SF is in the books! ๐ŸŽ‰ Come say hi to the team at Booth #214. We're excited to show how Tensormesh Platform can speed up AI inference and cut GPU costs with intelligent KV caching. See you on Day 2! #TheAIConference #AIInfrastructure #LLMInference #KVCache
1
4
8
194
I was delighted to give three keynotes recently, one at the 3rd HotInfra workshop at ISCA'26 (hosted by Prof. Jian Huang), one at the UIUC Systems Groups retreat (hosted by @tianyin_xu ), and a CMU guest lecture (hosted by Prof. Lei Li). The message was simple: KV cache is BEYOND cacheable intermediate states. It is what makes inference systems SMART. - If cached, it saves cost and reduces latency. - If analyzed, it reveals how the model attends to and understands context. - If optimized, it can improve not only performance, but also output quality. It's not a liability, but an ASSET --- (almost) always the more you have, the better. That is the part most people in industry still underestimate, even though the techniques are already here today: KV cache compression, blending, semantic reuse, cross-model sharing, attention steering, KV-cache-based retrieval, and more. The gap is not imagination. The gap is productization. KV cache will become a core AI-native data layer in future inference infrastructure โ€” not just something we store, but something we manage, analyze, and optimize. #KVCache, #LMCache, #LLMInference, #Tensormesh, #vLLM, #SGLang, #MLSys, #HotInfra
2
5
2
68
6,940
Kuntai Du retweeted
Why not store KV cache permanently? In case you missed it, #IBM recently posted two blogs for ๐—น๐—น๐—บ-๐—ฑ + ๐—ž๐Ÿด๐—ฆ + ๐—Ÿ๐— ๐—–๐—ฎ๐—ฐ๐—ต๐—ฒ-based KV storage. Thrilled to keep building together. Avoiding recomputation is the goal, but itโ€™s still rare to see KV cache treated as shared, persistent infrastructure in real production deployments. Excited to see LMCache be part of this with IBM, a long-time collaborator of the LMCache community. Thrilled to keep building together. These two posts are a great look at what that can actually look like in practice: 1. Rethinking LLM Inference Economics with llm-d, LMCache, and IBM Storage Scale community.ibm.com/community/โ€ฆ 2. Deploying Distributed LLM Inference Service with IBM Storage Scale for KV Cache Offloading community.ibm.com/community/โ€ฆ Great read for anyone interested in fast yet cheap LLM inference. #LMCache #vLLM #Kubernetes #K8s #KVCache
2
8
314
Kuntai Du retweeted
๐Ÿ”ด Live from #GTC2026 On the floor with our Chief Scientist @this_will_echo and CTO #Yihua Chang โ€” #KVCache is the hottest topic of the day. Even Jensen opened with it. ๐ŸŽ™๏ธThey covered topics like: #CacheBlend, @lmcache 0.4.0. and the super cool collab with @nvidia around a bot called #reachy using LMCache under the hood for 20x speedup #GTC2026 #KVCache #LMCache #TensorMesh
3
15
606
๐Ÿš€ LMCache has officially been out for 1.5 years now! Within its success, LMCache has become the default KV-cache library for open-source LLM inference (CPU offload, P2P sharing, multi-backend storage, vLLM/SGLang integration, and more). As a PyTorch Foundation Ecosystem project, LMCache is now used by enterprise leaders across the industry (GKE, AWS, Nvidia's Dynamo, llm-dโ€ฆ). ๐Ÿค”Whatโ€™s the secret to our product?? ๐Ÿ”Ž Come see yourself: arxiv.org/pdf/2510.09665 โ™ฅ๏ธ A huge thank you to our contributors and community, youโ€™ve influenced what makes LMCache today. (@lmcache) #KVCache #LMCache #LLM #vLLM
5
2
16
1,685
Meta just solved the biggest problem in RAG! Most RAG systems waste your money. They retrieve 100 chunks when you only need 10. They force the LLM to process thousands of irrelevant tokens. You pay for compute you don't need. Meta AI just solved this. They built REFRAG, a new RAG approach that compresses and filters context before it hits the LLM. The results are insane: - 30.85x faster time-to-first-token - 16x larger context windows - 2-4x fewer tokens processed - Outperforms LLaMA on 16 RAG benchmarks Here's what makes REFRAG different: Traditional RAG dumps everything into the LLM. Every chunk. Every token. Even the irrelevant stuff. REFRAG works at the embedding level instead: โ†ณ It compresses each chunk into a single embedding โ†ณ An RL-trained policy scores each chunk for relevance โ†ณ Only the best chunks get expanded and sent to the LLM โ†ณ The rest stay compressed or get filtered out entirely The LLM only processes what matters. The workflow is straightforward: 1. Encode your docs and store them in a vector database 2. When a query arrives, retrieve relevant chunks as usual 3. The RL policy evaluates compressed embeddings and picks the best ones 4. Selected chunks are expanded into full token embeddings 5. Rejected chunks stay as single compressed vectors 6. Everything goes to the LLM together This means you can process 16x more context at 30x the speed with zero accuracy loss. I have shared link to the paper in the next tweet!
49
269
10
1,400
103,594
Kuntai Du retweeted
Yesterday we hosted our first LMCache office hours! Jiayi Yao, Research Engineer at Tensormesh and one of the top contributors, covered LMCache architecture, key performance optimizations, and benchmark results-based on the newly published technical report available at arxiv.org/pdf/2510.09665. You can watch the recording here: youtu.be/y14ruG6CNGE?si=ktbfโ€ฆ Join us for the next LMCache office hours on December 11. Register to get it added to your calendar: lmcache-officehours.zapier.aโ€ฆ
1
6
823
Kuntai Du retweeted
Thanks to @github for spotlighting vLLM in the Octoverse 2025 report โ€” one of the fastest-growing open-source AI projects this year. ๐Ÿ† Top OSS by contributors ๐Ÿš€ Fastest-growing by contributors ๐ŸŒฑ Attracting the most first-time contributors Trusted by leading open model communities and industry partners โ€” including NVIDIA, Meta, Red Hat, DeepSeek, Qwen, Moonshot, and others โ€” vLLM has become a preferred engine for efficient LLM inference. With almost 63K stars and 1800 contributors, this growth belongs to the community. Together, weโ€™re building an easier, faster, and cheaper LLM serving for everyone. ๐Ÿ‘‰gh.io/octoverse #vLLM #OpenSource #AIInfra #Octoverse
7
22
1
117
10,905
๐Ÿง‘โ€๐Ÿ’ป gpt-oss-safeguard Hackathon ๐Ÿง‘โ€๐Ÿ’ป Join us Dec. 8 in SF for the Open Safeguard Hackathon โ€” a collaborative event by OpenAI, ROOST & @HuggingFace to explore how open models can shape safer digital spaces and explore the future of open-weight reasoning and online safety. Apply to participate: events.openai.com/gpt-oss-saโ€ฆ
9
25
7
231
35,056
Kuntai Du retweeted
LMCache highlighted by CEO of Redis @rowantrollope at Redis Released SF 2025! ๐ŸŽ‰ Weโ€™re thrilled to partner with Redis, bringing KV cache acceleration to the infra ecosystem. #Redis #LMCache #AIInfra #LLM #Caching #SFTech #RedisReleased2025 ๐Ÿ“Œ PS: Our team @kobe_eee(Kobe) & @this_will_echo(Kuntai) are here at the conference todayโ€”happy to connect in person if youโ€™re around!
3
14
667
Kuntai Du retweeted
Good work and glad to see LMCache featured! ๐Ÿ˜€ Check out LMCache at github.com/LMCache/LMCache Also we have our own K8s distributed inference framework, the vLLM Production Stack: github.com/vllm-project/prodโ€ฆ
LLM inference is too slow, too expensive, and too hard to scale. ๐Ÿšจ Introducing llm-d, a Kubernetes-native distributed inference framework, to change thatโ€”using vLLM (@vllm_project), smart scheduling, and disaggregated compute. Hereโ€™s how it worksโ€”and how you can use it today:
1
7
625
Kuntai Du retweeted
๐Ÿš€๐— ๐—ผ๐—ผ๐—ป๐—ฐ๐—ฎ๐—ฐ๐—ธ๐—ฒ X ๐—Ÿ๐— ๐—–๐—ฎ๐—ฐ๐—ต๐—ฒ: KV Cache-centric Language Model Serving ๐Ÿš€ We're thrilled to announce a strategic collaboration between LMCache and Mooncake to pioneer a KVCache-centric Large Language Model (LLM) serving system! This partnership is set to redefine efficiency, scalability, and responsiveness for LLM applications. By uniting LMCache's cutting-edge KVCache management with Mooncake's robust and optimized backend infrastructure, we're unlocking new levels of performance for handling diverse LLM workloads. ๐—Ÿ๐— ๐—–๐—ฎ๐—ฐ๐—ต๐—ฒ will serve as the ๐—ฐ๐—ผ๐—ป๐—ป๐—ฒ๐—ฐ๐˜๐—ผ๐—ฟ between ๐— ๐—ผ๐—ผ๐—ป๐—ฐ๐—ฎ๐—ธ๐—ฒ and ๐˜ƒ๐—Ÿ๐—Ÿ๐—  to enable more cross-layer optimizations in LLM serving. โœจ ๐—ช๐—ต๐—ฎ๐˜ ๐˜๐—ต๐—ถ๐˜€ ๐—บ๐—ฒ๐—ฎ๐—ป๐˜€: For LMCache users: Leverage Mooncake's advanced transfer engine and KVCache storage for significantly boosted data distribution and system performance. For Mooncake users: Benefit from LMCache as the KVCache management layer, enabling flexible cache control and exciting future capabilities like CacheBlend. ๐Ÿ“ˆ ๐—ฃ๐—ฟ๐—ผ๐—ผ๐—ณ ๐—ถ๐—ป ๐—ฃ๐—ฒ๐—ฟ๐—ณ๐—ผ๐—ฟ๐—บ๐—ฎ๐—ป๐—ฐ๐—ฒ: Our joint integration with vLLM (LMCache + Mooncake Store) has shown remarkable results on a Qwen2.5-72B-Instruct model (8xH800 GPUs): โฌ‡๏ธ ~69% reduction in Average Time To First Token (TTFT) โฌ†๏ธ ~191% increase in Request Throughput โฌ†๏ธ ~185% increase in Output Token Throughput ...all thanks to efficient KVCache reuse! For full results, please refer to our blog post: blog.lmcache.ai/2025-05-08-mโ€ฆ ๐Ÿ”ฎ ๐—ง๐—ต๐—ฒ ๐—™๐˜‚๐˜๐˜‚๐—ฟ๐—ฒ ๐—ถ๐˜€ ๐—•๐—ฟ๐—ถ๐—ด๐—ต๐˜: We're already collaborating on next-gen improvements, including optimized KVCache eviction/placement, asynchronous scheduling, zero-copy transfers, and more flexible caching strategies. This is a significant step towards realizing the full potential of next-generation LLM serving architectures. Stay tuned for more updates! ๐—Ÿ๐—ฒ๐—ฎ๐—ฟ๐—ป ๐— ๐—ผ๐—ฟ๐—ฒ & ๐—–๐—ผ๐—ป๐—ป๐—ฒ๐—ฐ๐˜: ๐Ÿ‘‡ LMCache GitHub: github.com/LMCache/LMCache Mooncake Github: github.com/kvcache-ai/Mooncaโ€ฆ vLLM Production Stack: github.com/vllm-project/prodโ€ฆ LMCache Slack Space: join.slack.com/t/lmcacheworkโ€ฆ #LLMs #AIServing #KVCache #OpenSource #TechCollaboration #LMCache #Mooncake #PerformanceOptimization #MachineLearning #AIInfrastructure #Innovation
1
10
2
22
1,609
Kuntai Du retweeted
๐Ÿคฏ 78.8% p95 Inter-Token Latency reduction with LMCache + vLLM v1 P/D support ๐Ÿš€ In our previous blog, we introduced the integration of ๐—Ÿ๐— ๐—–๐—ฎ๐—ฐ๐—ต๐—ฒ with ๐˜ƒ๐—Ÿ๐—Ÿ๐—  ๐˜ƒ๐Ÿญ and NVIDIA's ๐—ก๐—œ๐—ซ๐—Ÿ library, enabling Prefill-Decode Disaggregation (PD) for LLM inference. Today, we're thrilled to share the benchmark results that validate this integration achieves state-of-the-art PD performance. With this new integration, ๐—Ÿ๐— ๐—–๐—ฎ๐—ฐ๐—ต๐—ฒ reduces p95 Inter-Token Latency (ITL) by ๐Ÿณ๐Ÿด.๐Ÿด%!! And the performance of distributed serving in vLLM v1 is now comparable and even lower than NVIDIA Dynamo in some cases! For full result, please refer to our technical blog: blog.lmcache.ai/2025-04-29-pโ€ฆ This achievement is the result of active collaboration with ๐—ก๐—ฉ๐—œ๐——๐—œ๐—” ๐——๐˜†๐—ป๐—ฎ๐—บ๐—ผ, leveraging insights from ๐—Ÿ๐— ๐—–๐—ฎ๐—ฐ๐—ต๐—ฒ to push performance boundaries. Introduction to Prefill-Decode (PD) Disaggregation A leading solution for resolving the LLM inference problem is Prefill-Decode Disaggregation. The core idea? Separate the resource-intensive "prefill" stage (processing the input prompt) from the "decode" stage (generating subsequent tokens). Without PD: New prefill requests can interrupt ongoing decode jobs, causing high tail latency for long outputs. With PD: Dedicated decoders can stream tokens without interruption, ensuring a smooth user experience. PD is rapidly becoming the default architecture in cutting-edge inference engines and production deployments. This is precisely where LMCache comes in. As announced in our previous blog, LMCache now provides the necessary integration with vLLM v1 and NVIDIA's NIXL to enable robust, disaggregated prefill. Quickstart documentation: docs.lmcache.ai/getting_starโ€ฆ LMCache + vLLM v1 + NIXL = PD at State-of-the-Art Speed Final Notes Disaggregated Prefill is rapidly becoming foundational for high-performance LLM inference. With LMCache's PD support for vLLM v1 + NIXL, we're bringing a robust, production-grade solution with state-of-the-art performance to the open-source community. We are proud of this step but believe there's always room for improvement. The LMCache Lab is collaborating closely with the vLLM team right now to explore even better designs for PD disaggregation. Stay tuned โ€“ we're just getting started! #LLM #AIOptimization #Inference #vLLM #LMCache #NVIDIA #NIXL #PrefillDecode #Performance #MachineLearning #DeepLearning #ArtificialIntelligence #MLOps
8
20
726
Kuntai Du retweeted
After feedback about our v0.8.4 benchmark for @deepseek_ai R1, we rerun it with suggested changes: vLLM no EP, SGLang updated v0.4.5 -> post1 and EP -> DP, TensorRT-LLM uses overlap scheduler and tuned parameters. We are seeing good results! So why was there a difference? ๐Ÿงต
8
36
11
320
80,149
Kuntai Du retweeted
๐Ÿš€ ๐—ง๐—ฒ๐—ป๐—ฐ๐—ฒ๐—ป๐˜ x ๐—Ÿ๐— ๐—–๐—ฎ๐—ฐ๐—ต๐—ฒ Collaboration: Integrating ๐— ๐—ผ๐—ผ๐—ป๐—ฐ๐—ฎ๐—ธ๐—ฒ Store for Enhanced LLM Inference Caching! ๐Ÿฅฎ๐Ÿฅฎ Excited to share insights from a powerful collaboration between Tencent engineers and the LMCache Lab team! ๐ŸŽ‰ With the help from Tencent Engineers, we've successfully integrated high-performance Mooncake Store into the LMCache ecosystem via the new MooncakeStoreConnector. LMCache acts as intelligent caching middleware for LLM inference engines like vLLM, significantly reducing VRAM usage and compute overhead. Our latest blog post dives deep into: ๐Ÿ”น LMCache's architecture and the role of Remote Connectors. ๐Ÿ”น A detailed look at the MooncakeStoreConnector implementation. ๐Ÿ”น How this integration enables using Mooncake Store for KV cache offload & reuse in vLLM. ๐Ÿ”น Guidance on extending LMCache with your own backend connectors. This collaboration highlights the power of open-source synergy in tackling real-world production challenges for large language models. Read the full technical breakdown here: blog.lmcache.ai/2025-04-22-tโ€ฆ ๐—Ÿ๐—ฒ๐—ฎ๐—ฟ๐—ป ๐— ๐—ผ๐—ฟ๐—ฒ & ๐—–๐—ผ๐—ป๐—ป๐—ฒ๐—ฐ๐˜: ๐Ÿ‘‡ LMCache GitHub: github.com/LMCache/LMCache Chat with the Devs: forms.gle/hfcUeBV5pqgmEWWF6 LMCache Slack: join.slack.com/t/lmcacheworkโ€ฆ vLLM Production-Stack Github: github.com/vllm-project/prodโ€ฆ #AI #LLM #MachineLearning #Caching #DistributedSystems #OpenSource #Tencent #LMCache #vLLM #PerformanceOptimization #KVStore #MooncakeStore #Tencent
1
9
3
24
2,573
Kuntai Du retweeted
OpenRLHF is a pioneering framework to use vLLM for RLHF, driving many design and implementation of vLLM's features for RLHF, making vLLM a popular choice for many RLHF frameworks. Learn more about the story at blog.vllm.ai/2025/04/23/openโ€ฆ
40
40
6
259
48,180
Please stop attacking vLLM teamโ€™s integrity and being defensive about benchmarks involving SGLang. If you think the results are incorrect, please submit a PR to the open benchmark repo to correct the results.
I'm glad to see you've made some corrections. You can express humility by avoiding absolute statements like "We did not publish misleading results" or "We never misrepresent results." How can you claim your previous results weren't misleading when your new TRT-LLM results are 2x faster on ShareGPT and 1.6x faster on 1k-in-2k-out compared to your previous TRT-LLM results? The same applies to SGLang. Reproducibility and misleading results are distinct issues. One can produce reproducible yet misleading results by configuring an engine suboptimally, as you did in the previous post. Everyone makes mistakes, and it's perfectly fine to acknowledge them rather than being defensive. I also find it challenging to benchmark these engines correctly due to their many advanced options. This could become an endless battle, as engines improve daily, so I'd prefer to stop here and focus on real work. See also: teapawt.org/zhyncs42/status/191353โ€ฆ
5
6
6
213
51,658