Skip to content

Topic

LLM Inference Serving

Field covering engines (vLLM, SGLang, Ollama) and techniques like KV caching, PagedAttention, and batching that run trained LLMs efficiently in production.

Current stories

buildOne report1 publisher

Beam search outside vLLM's GPU engine pushed Spotify's podcast recommender onto lower-tier hardware

Spotify launched LLM podcast recommendations in January 2026 on lower-tier GPUs because vLLM's beam search left high-end hardware underused. Its post on a collaboration with NVIDIA on TensorRT LLM starts from that constraint.

Publishers:engineering.atspotify.com

Reality

Evidence40
Adoption
Not scored
Hype gap
Not scored
Incentives50
Confidence50
buildOne report1 publisher

A clean config diff against Qwen3.8-27B does not let AREX-2 reuse the base model's serve command

BAAI's AREX-2 config declares one multi-token-prediction layer, but its weight index lists 0 such tensors against Qwen3.8-27B's 15. Its dev.to testers say the base-model drafter and quant need rechecking too, though they have not run AREX-2.

Publishers:dev.to

Reality

Evidence55
Adoption
Not scored
Hype gapβˆ’10
Incentives
Not scored
Confidence50
buildOne report1 publisher

EcoHash gets nearly 2x from a dense 27B's built-in draft head on a single 96 GB card

EcoHash reports that one vLLM flag took Qwen3.8-27B on a single RTX Pro 6000 from 999.9 to 1954.0 output tokens/sec. The figure comes from its own production config on vLLM 0.27.1, so it is one team's measurement on its own workloads.

Publishers:dev.to

Reality

Evidence45
Adoption
Not scored
Hype gap+12
Incentives70
Confidence50
buildOne report1 publisher

LMCache multiprocess mode runs pickle.loads on whatever reaches its unauthenticated socket

JFrog disclosed an unauthenticated remote code execution flaw in LMCache's multiprocess mode, CVE-2026-105192, rated CVSS 9.8 with no patch. A public proof of concept exists, so any deployment that exposes the cache server to a network needs access limits or the mode turned off.

Publishers:dev.to

Reality

Evidence55
Adoption
Not scored
Hype gap+15
Incentives
Not scored
Confidence50
buildOne report1 publisher

vLLM 0.32.0rc0 denies cross-origin browser calls unless operators list their origins

vLLM 0.32.0rc0 sets the --allowed-origins default to an empty list, where 0.31 and every release back to 0.6 allowed all origins. A dev.to write-up says browser UIs on another origin will break on upgrade while server-side clients keep working.

Publishers:dev.to

Reality

Evidence68
Adoption
Not scored
Hype gapβˆ’5
Incentives
Not scored
Confidence65
buildOne report1 publisher

One 80 GB GPU holds 4-bit 70B weights and at most 11 conversations of 8,192 tokens

Serving a 70B model takes about 141 GB of GPU memory for weights at 16-bit, 73 GB at FP8 and 40 GB at 4-bit, according to a dev.to post. Fine-tuning takes about 50 GB with QLoRA and 1.1 TB with full AdamW. The post maps both onto GPU setups and hourly rental prices.

Publishers:dev.to

Reality

Evidence72
Adoption
Not scored
Hype gap+5
Incentives
Not scored
Confidence68
buildOne report1 publisher

NVIDIA and Princeton cache SSM inputs in place of state to speed hybrid-model decoding

NVIDIA and Princeton's Dao AI Lab cache SSM inputs instead of state, targeting a decode step where SSM layers are the largest component up to 100K tokens. ReplaySSM is already integrated into TensorRT-LLM, vLLM and FlashInfer, NVIDIA says.

Reality

Evidence45
Adoption
Not scored
Hype gap
Not scored
Incentives55
Confidence50
buildOne report1 publisher

llama-server's default prompt cache mixes two LoRA scales into one answer

llama-server's default prompt cache restored KV built under the wrong LoRA scale on 10 of 10 test prompts in release b11514. According to the dev.to write-up that found it, servers that swap adapters per request behind a shared system prompt trigger it all day.

Publishers:dev.to

Reality

Evidence68
Adoption
Not scored
Hype gap+10
Incentives20
Confidence62
buildOne report1 publisher

vLLM's build now imports setuptools_rust unguarded, and that makes Rust non-optional

A dev.to walk-through pins the change to line 21 of setup.py: no try, no feature flag. Build vLLM from source and you own a Rust toolchain, plus a protoc you were never told about.

Publishers:dev.to

Reality

Evidence55
Adoption
Not scored
Hype gap+15
Incentives
Not scored
Confidence50
buildOne report1 publisher

Sluice puts a doorman in front of vLLM, because vLLM cannot tell who paid

Design notes for a QoS proxy make a narrow, useful argument: on a fixed GPU pool, tier promises are only real if something admits or sheds requests before the engine sees them.

Publishers:dev.to

Reality

Evidence35
Adoption
Not scored
Hype gap+10
Incentives55
Confidence40
buildOne report1 publisher

Patterned PEFT LoRA adapters run at the wrong scale in vLLM 0.30.0

vLLM 0.30.0 ignores the per-module rank and alpha patterns in PEFT LoRA adapters, and one test put the error against PEFT at 70 times the unpatterned baseline. The adapter loads without complaint, so only a config check or a side-by-side against PEFT will catch it.

Publishers:dev.to

Reality

Evidence64
Adoption
Not scored
Hype gap+12
Incentives20
Confidence66
buildOne report1 publisher

vLLM 0.30.0's weight cache serves a cached model to any checkpoint with the same layout

vLLM 0.30.0's weight cache fingerprints only safetensors headers, letting an engine on an altered Qwen3-0.6B run the daemon's original weights. Fine-tunes share their base model's headers, so a mix-up there would produce fluent wrong answers under a log line reporting success.

Publishers:dev.to

Reality

Evidence64
Adoption
Not scored
Hype gap+8
Incentives30
Confidence62
buildOne report1 publisher

Helion's autotuned GEMM outruns vLLM's CUTLASS and DeepGEMM paths on Hopper GPUs

Helion's autotuned GEMM beat vLLM's default CUTLASS and DeepGEMM backends on Hopper GPUs, by more than 10% throughput on some workloads, its authors report. The gain rests on per-shape tuning that can run for hours, a cost teams pay in place of kernel maintenance.

Publishers:pytorch.org

Reality

Evidence35
Adoption15
Hype gap+10
Incentives70
Confidence40
buildOne report1 publisher

AgSpec nearly doubles speculative draft length by indexing code the way coding agents write it

KAIST and Seoul National University's AgSpec nearly doubles accepted draft length for coding agents by indexing files in the diff and JSON forms agents emit. It lives entirely in the retrieval index and leaves model weights untouched.

Publishers:dev.to

Reality

Evidence45
Adoption
Not scored
Hype gap+15
Incentives
Not scored
Confidence40
buildOne report1 publisher

Microsoft publishes token and cache telemetry from 301,026 Copilot agent sessions

Microsoft released metadata from 301,026 GitHub Copilot agent sessions, covering 9.3 million LLM calls in one June week. Capacity planners now have real cache and token figures to test against, though the files measure resource use only and cannot show whether the output was any good.

Publishers:runtimewire.com

Reality

Evidence64
Adoption
Not scored
Hype gapβˆ’5
Incentives45
Confidence60
buildOne report1 publisher

SageMaker charges 1.40x EC2's hourly rate for the same Gemma 4 server on the same GPU

SageMaker costs 1.40x a plain EC2 instance per hour to serve one Gemma 4 vLLM build on the same T4 or L4 GPU, a benchmark on dev.to finds. With decode speed matched within 2%, the extra 40% goes to the managed layer around the GPU.

Publishers:dev.to

Reality

Evidence60
Adoption
Not scored
Hype gap+5
Incentives
Not scored
Confidence60
buildOne report1 publisher

Halving vLLM's attention tiles puts Gemma 4 on SageMaker's smallest GPU at 0.8x L4 speed

Gemma 4 decodes on SageMaker's smallest GPU, a T4, at 0.8x an L4's speed with matching outputs from a patched vLLM image, a dev.to benchmark reports. The T4 is the cheaper choice per token only when it rents for under 80% of the L4's hourly rate.

Publishers:dev.to

Reality

Evidence45
Adoption
Not scored
Hype gap+15
Incentives35
Confidence40
buildOne report1 publisher

Repacked 4-bit embeddings lift Gemma 4 decode up to 1.39x on a single L4

Repacking Gemma 4's QAT weights with 4-bit embedding tables made decode up to 1.39x faster on one SageMaker L4, according to a dev.to benchmark series. For teams serving Gemma 4 on vLLM, how the weights are stored becomes a setting to measure alongside model size.

Publishers:dev.to

Reality

Evidence55
Adoption
Not scored
Hype gap+10
Incentives
Not scored
Confidence50
buildOne report1 publisher

Deployment held up under concurrent load after targets fell to 131,072 tokens and 16 sequences

Qwen Flash-Next NVFP4 ran in vLLM at 131,072 tokens of context and 16 sequences only after loader patches and cuts to its original targets. Its one load test covers only the bfloat16 KV-cache baseline, so operators on the later B12x stack have to run their own.

Publishers:dev.to

Reality

Evidence45
Adoption8
Hype gap0
Incentives
Not scored
Confidence40

Earlier coverage

  1. A 30B model that activates 3B still has to keep all 30B in VRAM

    Build Β· September 15, 2026 Β· One report1 publisher

  2. Decode drags the entire model out of VRAM once per word

    Build Β· August 31, 2026 Β· One report1 publisher