#inference deployment

30 stories · 7 in 7 days · 18 in 30 days
Stories, products and papers tagged "inference deployment", newest first.
Nov 13
ProductsBuildersOfficial06:27
Chinese contentSGLang-Neuron 上线 AWS Deep Learning Container,支持在 Trainium 上部署大模型

SGLang 用户现在可以直接把推理和 RL rollout 跑到 AWS Trainium 上,接口不变、原生 PyTorch、AWS 官方容器开箱即用。想在 GPU 之外降推理成本或统一训练推理硬件的团队可以试试这条路。

Event
Primary sourceAWS Machine Learning Blog@Alex NailsSource
ProductsBuildersMulti-sourceSelected06:06
SGLang-Neuron brings SGLang serving to AWS Trainium

Serving stacks have mostly been GPU-bound, so a Trainium path for SGLang reduces the engineering cost of running inference on AWS's own silicon. Teams standardising on SGLang for RL rollout generation can now target Trainium instances directly. This matters for anyone evaluating Trainium against NVIDIA GPUs for cost or supply reasons, since the same APIs carry over.

Event
Official accountAmazon Science@AmazonScienceSource
ProductsBuildersMulti-sourceSelected03:03
CoreWeave webinar on hot-swapping RL checkpoints in production

The non-obvious point is that RL cadence, not compute size, becomes the serving bottleneck once weights update every few hours, and hot-loading removes the downtime tradeoff. ML platform engineers and inference teams running post-training pipelines should attend to copy the Dynamo and RL Rollouts setup directly, including cost figures. Comparing on-policy weight transition approaches before committing to an orchestration stack could save a costly rework later.

Event
CoreWeave@CoreWeaveSource
Nov 11
How-toBuildersSelected01:14
vLLM Adopts PyTorch LibTorch Stable ABI to Cut Rebuilds

The change removes a recurring pain point: version lockstep between inference engines and the PyTorch runtime. Platform engineers and ML infrastructure teams deploying vLLM can now mix torch versions with less risk, accelerating security and performance updates. Distributors and package maintainers benefit most, since rebuild effort drops sharply across release cycles.

Official accountvLLM@vllm_projectSource
Nov 10
Nov 7
Nov 6
Nov 5
Oct 23
ModelsBuildersSelected11:25
MiniMax M3.1 Flash Runs in Production on vLLM

Production-grade serving of a MiniMax model through vLLM signals that the open-source inference stack can now carry commercial workloads with SLA guarantees. Teams evaluating cheaper open-weight serving options can look at Inferact's vLLM-based offering as a reference setup. Upstream contributions also mean the wider vLLM community inherits the reliability hardening that came out of this deployment.

Official accountvLLM@vllm_projectSource
Oct 21
ProductsBuildersSelected01:17
vLLM TorchTPU backend brings Google Cloud TPUs into vLLM ecosystem

Serving infrastructure built around NVIDIA GPUs now has a maintained TPU path, lowering the switching cost for teams that want Google's accelerator pricing and capacity. Contributors can apply for the free TPU pool to test and port models. Practitioners running vLLM in production should evaluate TPU serving costs against their current GPU fleet.

Xianbao Qian@Xianbao_QIANSource
Oct 20
Oct 19
How-toBuildersSelected09:22
vLLM cuts startup time 14–18% with precompiled Python bytecode

Image-level bytecode caching means faster pod spin-up and less wasted GPU time for anyone running vLLM at scale, especially on autoscaling or serverless deployments where cold starts hurt. Engineering teams deploying inference can pick it up by using release images from v0.32.0 or the CUDA nightlies, with no workflow change beyond the image tag.

Official accountvLLM@vllm_projectSource
Oct 16
Oct 14
ProductsBuildersMulti-sourceSelected23:48
Intel Inference Microservices auto-tune vLLM on Xeon 4-6 CPUs

The tuning work most teams skip — NUMA layout, AMX activation, vLLM flags — is now baked into a container, so existing Xeon fleets can serve LLMs without days of manual optimization. Teams running inference on CPU-only infrastructure should try the detect-hardware and dry-run commands to preview the exact vLLM settings before deploying. It positions Intel's CPU lineup as a cheaper alternative to GPU-based serving for steady-state inference workloads.

Event
IT之家Source
Oct 13
ProductsBuildersSelected04:26
llm-d to share inference scaling update at PyTorch Conference

Beyond the benchmark framing, the notable shift is that open source inference serving now covers day-two operations — multi-tenant QoS and zero downtime — which were previously the gap against managed inference platforms. Platform and MLOps engineers running self-hosted LLM serving on Kubernetes stacks can evaluate llm-d as an alternative to vendor-managed serving. Details will land at the PyTorch Conference sessions.

Official accountPyTorch@PyTorchSource
Oct 4
Sep 28
How-toBuildersSelected73°00:57
Red Hat talk on enterprise agentic inference at PyTorch Conference

The gap between pilot demos and always-on enterprise serving is now being closed inside the PyTorch and vLLM ecosystems, meaning teams no longer need proprietary stacks for reliable agentic workloads. Platform engineers and ML infrastructure leads evaluating serving stacks can benchmark vLLM's enterprise features against alternatives. Developers of independent tools can also learn how Ecosystem Landscape membership raises their project's visibility.

Official accountPyTorch@PyTorchSource
Sep 26
How-toBuildersSelected76°15:03
vLLM Adds Elastic Expert Parallelism for Live MoE GPU Scaling

Serving MoE models usually means over-provisioning GPUs to absorb traffic spikes, so resizing clusters without downtime directly cuts inference cost. Engineers running vLLM in production get a concrete mechanism via NIXL EP to scale expert-parallel workers on demand. The PyTorchCon 2026 session will be the reference for implementation details and known limitations.

Event
Official accountPyTorch@PyTorchSource
Aug 7
Jul 28
Jul 20
Jun 12
May 30
May 29