All articles (page 3)

Costs

MLPerf Endpoints: can inference providers finally be compared?

MLPerf Endpoints measures an inference service through its API at several load levels. Version 0.7 finally traces the curve between throughput, TTFT, TPOT and quality, but it does not normalize cost yet.

12 min read
  • MLPerf
  • LLM Inference
  • Benchmark
  • TTFT

Silicon

UALink 2.0 vs NVLink 6: when the network computes all-reduce

UALink 2.0 standardizes compute inside the network; NVLink 6 integrates it into its switches. Here is what the mechanism changes, and why Helios and Vera Rubin still cannot be ranked.

14 min read
  • UALink 2.0
  • UALoE
  • NVLink 6
  • in-network compute

Runtimes

DWDP for MoE inference: move weights, not tokens

Expert parallelism moves tokens to weights. DWDP reverses the path, prefetching remote expert weights and removing cross-rank synchronization. The bet works inside a narrow regime.

11 min read
  • DWDP
  • MoE
  • SGLang
  • TensorRT-LLM

Silicon

RTX PRO 6000 or three RTX 5090s: 96 GB is not one memory pool

An RTX PRO 6000 and three RTX 5090s each add up to 96 GB of GDDR7. For an LLM, that is where the equality ends: one pool, one sharded model and three independent replicas pay different costs.

10 min read
  • RTX PRO 6000
  • RTX 5090
  • Local LLM
  • multi-GPU

Runtimes

vLLM 0.27 turns the KV cache into peer-to-peer memory

vLLM 0.27 lets every engine serve CPU-resident KV blocks to another peer over NIXL, filters tiers per request and emits routable cache events. The mechanism is shipped; the production speedup is not proven.

11 min read
  • vLLM 0.27
  • KV cache
  • NIXL
  • Offloading

Silicon

RTX Spark on Windows: CUDA is native, the LLM stack is not yet

RTX Spark brings up to 128 GB of unified memory and native CUDA to Windows on Arm. As of August 12, CUDA remains a developer preview, TensorRT-RTX is ready, and the LLM serving stack still needs qualification.

11 min read
  • RTX Spark
  • Windows on Arm
  • CUDA 13.4
  • TensorRT-RTX

Runtimes

Kimi K3 opens 2.8T parameters, not a local model

Kimi K3 activates 104 billion parameters out of 2.8 trillion, mixes KDA with MLA across a one-million-token context, and needs an eight-B300 or eight-MI355X node in vLLM's launch recipes.

9 min read
  • Kimi K3
  • Moonshot AI
  • MoE
  • KDA

Runtimes

Latency against latency: what your scheduler actually decides

An inference engine's scheduler does not trade throughput against latency. It trades one latency against another: time to first token versus time between the tokens that follow. Three major engines, three opposite defaults, and nothing tells the operator.

18 min read
  • Scheduler
  • vLLM
  • SGLang
  • TensorRT-LLM

Runtimes

MoE serving: at what batch size does the network take over?

A mixture-of-experts does not remove the cost, it moves it twice: from compute to memory, then from memory to the network. The second shift has a threshold, it can be computed, and it decides your topology.

25 min read
  • MoE
  • Expert parallelism
  • all-to-all
  • DeepEP

Costs

What stops a driving model from crossing a border

A driving model is a function of its data distribution. But the cost of moving it is not where intuition puts it: perception recalibrates for almost nothing, behaviour does not, and validation dominates everything. The entry price for a market is a simulation bill.

20 min read
  • Autonomous driving
  • Validation
  • Simulation
  • UNECE