The name is the button.

An agent writes the code now, and a human thumb hovers over Accept all a hundred times a day. The honest question of this decade is what, exactly, you just accepted. So I read the diff.

Eight years as a backend engineer in Stockholm, back in Tokyo since 2023, and I still ship something small most nights, usually badly. My one rule: the only real review of a model is the thing you built with it. That is why there is no leaderboard on this site.

Around a hundred and forty sources come through — the labs' own posts, the papers, the tools, the runtimes and languages nobody is watching yet, the chip under the demo, and the newsletters people actually forward. What is moving gets counted so the week reads at a glance, and every few days I explain one mechanism in plain words.

A story here is a headline, a short excerpt, one image and the link to whoever wrote it. We never reproduce the post; the images belong to their authors. A post written in Japanese appears in Japanese, exactly as it was published, and the link goes to the original.

— Yuki Halvorsen, Tokyo

← Accept All Archive

vLLM BlogTools

Taking vLLM Apart: A Practical Guide to Disaggregated Serving

09.29

What disaggregated serving actually buys you, how to run it end to end in vLLM today with prefill/decode plus the new GPU-less frontend and the things we're still working on.

Open weights disaggregation

Read at vLLM Blog ↗

One letter a week, starting soon.

Latest

Taking vLLM Apart: A Practical Guide to Disaggregated Serving

Related

ToolsWatermarking in vLLM vLLM Blog

ToolsReducing vLLM startup time with one uv flag vLLM Blog

ToolsAnnouncing vllm-metal: Concurrent Serving on Apple Silicon vLLM Blog

ToolsScaling Multi-GPU Video Captioning with PyNvVideoCodec and vLLM vLLM Blog

ToolsvLLM x Novita AI: Chord, Faster INT4 MoE for Kimi K2.x. Up to 1.3x on H200, 2.15x on Untuned B300 vLLM Blog

ToolsKimi K3 Performance Optimizations in vLLM: The Road to 2.8× Throughput vLLM Blog