AIDC
DC AI 热点

精选

当前热点完整榜单 →
1微软发布新版Copilot超级应用:整合聊天、编程与智能体能力82 热度 ⌁2Anthropic 与 Akamai 达成 116 亿美元云算力协议,年内算力支出承诺已超 5000 亿美元80 热度 ⌁3谷歌启动Project Suncatcher:计划下周开展首个太空轨道数据中心测试79 热度 ⌁4马斯克披露AI算力布局:Colossus集群拟部署超百万张英伟达GB300芯片78 热度 ⌁5微软正式推出新版 Copilot“超级应用”,整合聊天、代码与智能体能力77 热度 ⌁
9月11日2026-09-11
vLLM 更新✦ 精选规则精选07:53

v0.29.0

v0.29.0 Highlights This release features 594 commits from 277 contributors (91 new)! Model Runner V2 is now the default for all models ( #53183 ), completing the rollout that began with pooling models ( #48290 ). MRV2 also gained CUDA graph memory profiling for KV cache auto-sizing ( #53306 ), batch-sharded sampling that cuts per-step logits memory by 1/TP ( #50465 ), prompt embeds ( #42963 ), extract_hidden_states speculation ( #49811 ), padded FULL cudagraph dispatch for uniform decode under spec decode ( #53407 ), and DP-sync skipping before EAGLE/MTP draft prefill ( #53694 ). MRV1 remains in use for a few ROCm models and features MRV2 doe

Kubernetes Blog✦ 精选规则精选02:30

Kubernetes v1.37: Scheduler Preemption for In-Place Pod Resize (Alpha)

In Kubernetes, resource allocation has historically been a static decision made during a Pod's initial scheduling and placement. With the graduation of the core in-Place Pod resize feature to General Availability in v1.35, application developers and cluster operators gained the powerful ability to dynamically adjust CPU and memory allocations of running containers without incurring disruptive restarts or application downtime. However, in-place resizing introduced a unique resource scheduling gap: if a running Pod requested a resource scale-up that exceeded the host node's allocatable headroom, the Kubelet was forced to mark the request as Def

9月10日2026-09-10
AWS Architecture✦ 精选规则精选05:05

Validating multi-Region DR for Terraform Enterprise with AWS FIS

Learn how AWS, HashiCorp, and Athenahealth designed and chaos-tested a multi-Region disaster recovery strategy for Terraform Enterprise on AWS. This post walks through three-phase AWS Fault Injection Service experiments across Amazon EC2, Aurora, and Amazon S3, the 12-14 minute recovery times achieved, and the state file dependency pitfall to avoid.

vLLM 官方博客(网页)✦ 精选规则精选00:00

Tiered KV Cache Offloading in vLLM

A host-centric framework for scaling KV cache across host memory, filesystems, object stores, and remote peers — reducing recomputation and increasing serving c

9月9日2026-09-09
9月8日2026-09-08
vLLM 更新✦ 精选规则精选16:34

v0.29.0rc6

[Bugfix][Core] Apply dense prefix cache default to hybrid models ( #55 …

9月7日2026-09-07
9月5日2026-09-05
Equinix Blog · 互联基础设施✦ 精选规则精选19:55

Equinix Horizon 2026: The Recap

Equinix has been in business for 28 years and just held our first ever customer event this week. Equinix Horizon changed that, bringing together…

9月3日2026-09-03
9月2日2026-09-02
9月1日2026-09-01
8月28日2026-08-28
Kubernetes Blog✦ 精选规则精选02:30

Kubernetes v1.37: Metrics API graduates to stable

Kubernetes v1.37 promotes the metrics.k8s.io API to stable ( v1 ). This API provides CPU and memory usage for nodes and Pods, and is the API behind commands such as kubectl top and resource-metrics-based autoscaling. For cluster operators and application developers, this graduation means that the API now has the stability guarantees associated with a Kubernetes stable API. The v1 API has the same resource types and fields as v1beta1 ; this is an API-version graduation, not a change to the metrics that are collected or returned. A long-lived API reaches stable The resource Metrics API was introduced as alpha in Kubernetes v1.6 and became beta

8月27日2026-08-27
8月26日2026-08-26
AWS HPC✦ 精选规则精选06:33

Part 1: Managing Large-Scale LLM Training with AWS ParallelCluster

This post references AWS ParallelCluster. Check out AWS Parallel Computing Service (AWS PCS), our new managed Slurm service for running HPC and AI workloads on AWS. Introduction The Korean Government announced a national AI initiative to provide high-performance GPU infrastructure for Korea’s national AI research teams. AWS was selected as a supplier of GPU resources […]