News

LMCache at Samsung: The Right People in the Right Place

2026-10-28

KKarsten Wade

Another small but important milestone occurred for the project with this inaugural event bringing LMCache meetups to the San Francisco Bay Area.

On Thursday, 22 October 2026, engineers and researchers who work on KV cache management met LMCache maintainers and contributors at Samsung Semiconductor in San Jose. The event was “Elevate Your LLM Performance: LMCache Meetup + Hands-on Workshop,” a free, four-hour afternoon during Open Source AI Week. Dongjoo Seo of Samsung and I co-hosted, and Samsung provided the venue.

Our goal was to move people from listening to experimenting. Many attendees got LMCache running locally on their laptop and began experimenting with KV cache management before the event ended.

The word among event organizers is, “Everyone knows that people sign up for free events with no plan to attend.” Measured against our own baseline, turnout was double what we expected. More important, it was the right people in the right place.

Attendees with laptops sit at long rows of tables in a large meeting room at Samsung Semiconductor in San Jose. Samuel Shen stands at the podium and Dongjoo Seo holds a microphone near the stage, below a slide titled 'kv cache speedup: compute vs throughput.'
Samuel Shen of Tensormesh at the podium and Dongjoo Seo of Samsung with the microphone, at Samsung Semiconductor in San Jose, 22 October 2026.

Who came

Registrants came from hardware, memory, storage, and silicon companies, from universities, and from AI startups. Many of them build the systems where KV cache offload lands. That is the audience LMCache most needs to hear from.

The program

I opened with an introduction to LMCache. My slides are in the lmcache-blogs repo.

LMCache contributor Samuel Shen then led a 45-minute, hands-on deep dive using a Jupyter notebook. Sam also built the notebook so you can run it on your own laptop, with no GPU: lmcache-cpu-demo. It starts two copies of vLLM on your CPU with the same small model, Qwen/Qwen2.5-0.5B-Instruct. One copy is plain vLLM. The other sends its KV cache to an LMCache server that keeps it in RAM and also writes it to disk. Both copies have vLLM’s own prefix cache turned off, so every cache hit you see comes from LMCache.

The notebook loads a 6,000-token document, the Wikipedia article on Samsung, as a shared prefix. You then ask questions about it in a side-by-side UI and compare the time to first token. On the first question, both sides compute the document. From the second question on, the plain side computes it again each time, and the LMCache side gets it back from the cache.

If you missed the workshop, start with Sam’s notebook. Let me know in the comments or social media how things worked out with the notebook.

Following Sam, Luis Chamberlain of Samsung gave a technical session on three topics: asymmetric quantization, dma-buf support with io_uring, and learned prefix caching with Cartridges and the work that follows from it. Cartridges is one of the research ideas listed on lmcache.ai.

Luis’s slides are online, and there is a PDF copy in the event folder.

Dongjoo Seo of Samsung closed the talks with LMCache on CXL (Compute Express Link) memory. His slides are found as PowerPoint and PDF in the lmcache-blogs repo.

Dongjoo Seo speaks beside a Samsung podium. Behind him, a large screen shows a slide titled 'Three ways it can be set up,' a table comparing Device-DAX L1, DRAM L1 plus DAX L2, and shared L1. Attendees with laptops watch from the tables in front.
Dongjoo Seo of Samsung shows three ways to set up LMCache on CXL memory.

For more of Samsung’s work with LMCache, read their September post, Raw block in LMCache: building a fast, recoverable NVMe tier for KV cache.

The afternoon ended with closing remarks and a networking reception.

In particular, I welcomed everyone to the new LMCache meetup community. Then I invited participation in helping organize and execute future meetups.

What you told us

Rows of attendees with laptops face a screen at the front of the room. In the middle row, one attendee holds a microphone to ask a question.
Attendees ask questions during the talks.

Registration answers showed us how people run inference today. About 60 percent of registrants run vLLM, and about 30 percent run SGLang. About 65 percent run agent workloads. Long context, retrieval-augmented generation (RAG), and multi-turn chat came next.

You also told us what you want from the maintainers. The most common requests were:

  1. A production deployment guide.
  2. Reproducible benchmarks on your own stack.
  3. A clear comparison between LMCache and the prefix caching built into vLLM.
  4. An honest view of how good SGLang support is today.

This list helps us decide where to spend time. If one of these requests is yours, tell us more about your setup in the LMCache Slack.

Thank you, and what comes next

Thank you to Samsung for hosting us, to Luis and Dongjoo for their talks, and to Sam for building and running the hands-on session.

Here is how to continue:

We will see you at the next one.

Table of Contents

Share via:

Leave a Reply

This site uses Akismet to reduce spam. Learn how your comment data is processed.

More from the blog