惯性聚合 高效追踪和阅读你感兴趣的博客、新闻、科技资讯
阅读原文 在惯性聚合中打开

推荐订阅源

Hacker News - Newest:
Hacker News - Newest: "LLM"
Project Zero
Project Zero
The Hacker News
The Hacker News
博客园 - Franky
博客园_首页
云风的 BLOG
云风的 BLOG
T
Tenable Blog
腾讯CDC
量子位
大猫的无限游戏
大猫的无限游戏
Cyberwarzone
Cyberwarzone
让小产品的独立变现更简单 - ezindie.com
让小产品的独立变现更简单 - ezindie.com
IT之家
IT之家
B
Blog
C
Cybersecurity and Infrastructure Security Agency CISA
宝玉的分享
宝玉的分享
T
The Blog of Author Tim Ferriss
P
Privacy & Cybersecurity Law Blog
小众软件
小众软件
Vercel News
Vercel News
Blog — PlanetScale
Blog — PlanetScale
The Cloudflare Blog
G
Google Developers Blog
Security Latest
Security Latest
I
Intezer
C
Cyber Attacks, Cyber Crime and Cyber Security
阮一峰的网络日志
阮一峰的网络日志
Cyber Security Advisories - MS-ISAC
Cyber Security Advisories - MS-ISAC
A
Arctic Wolf
Microsoft Security Blog
Microsoft Security Blog
O
OpenAI News
AWS News Blog
AWS News Blog
WordPress大学
WordPress大学
MongoDB | Blog
MongoDB | Blog
C
Cisco Blogs
T
Tor Project blog
博客园 - 【当耐特】
有赞技术团队
有赞技术团队
Last Week in AI
Last Week in AI
Google DeepMind News
Google DeepMind News
奇客Solidot–传递最新科技情报
奇客Solidot–传递最新科技情报
人人都是产品经理
人人都是产品经理
aimingoo的专栏
aimingoo的专栏
J
Java Code Geeks
D
Docker
A
About on SuperTechFans
H
Hackread – Cybersecurity News, Data Breaches, AI and More
N
News and Events Feed by Topic
Hacker News: Ask HN
Hacker News: Ask HN
Help Net Security
Help Net Security

Amazon Science homepage

Amazon and University of Michigan give robots a sense of touch Capturing token IDs during agentic interactions for better reinforcement learning How Amazon tracks carbon intensity across its operations The fuel of the future is already here: Why TRISO matters AWS Graviton5: How a new chiplet architecture delivers 25% better performance - Amazon Science How formal verification makes AWS Nitro the first formally verified cloud hypervisor - Amazon Science Four approaches to grounding AI agents in the physical world - Amazon Science Bridging intent and execution in agentic systems - Amazon Science Ground truth is a process, not a dataset - Amazon Science Amazon Research Awards recipients announced - Amazon Science Training LLMs to reason in oarallel: How global forking tokens improve accuracy - Amazon Science New scaling law connects LLM architecture to inference efficiency, boosting throughput up to 47% - Amazon Science Promptimus: Improving already good LLM prompts with zero manual engineering - Amazon Science How Amazon optimizes middle-mile delivery networks under uncertainty - Amazon Science How mechanism design theory helps optimize Amazon-vendor collaboration - Amazon Science Inside Amazon's responsible-AI pipeline - Amazon Science How to train AI on private data without exposing it - Amazon Science How catastrophic is your LLM? A statistical framework for certifying conversational risk - Amazon Science Isabelle/HOL: The proof assistant behind the Nitro Isolation Engine - Amazon Science Customized Amazon Nova models improve molecular-property prediction in drug discovery - Amazon Science AWS and Hopkins Engineering announce groundbreaking database for AI/ML antibody design - Amazon Science How Amazon uses agentic AI for vulnerability detection at global scale - Amazon Science Verifying and optimizing post-quantum cryptography at Amazon - Amazon Science Improving quality and robustness in LLM-based text-to-speech systems - Amazon Science Formally verified AES-XTS: The first AES algorithm to join s2n-bignum - Amazon Science Optimizing LoRA target module selection for efficient fine tuning - Amazon Science How agentic AI helps heal the systems we can’t replace - Amazon Science Designing user experience for agentic AI: A framework for human-AI coordination - Amazon Science How AI is changing the nature of mathematical research - Amazon Science Intelligence isn’t about parameter count. It’s about time. - Amazon Science Why a 12-year-old forecasting paper has stood the test of time - Amazon Science How academic collaboration delivers real-world security to Amazon customers - Amazon Science Amazon Nova AI Challenge returns with Nova Forge access for competing teams - Amazon Science
How flat is replacing fat in AWS data center networks - Amazon Science
Giacomo Bernardi, Ratul Mahajan, Seshadhri Comandur · 2026-05-28 · via Amazon Science homepage

Routing in today’s data centers is usually governed by a data structure called a “fat tree”, which is similar to a corporate organizational chart, with nodes in each layer connecting to multiple nodes in the layer below. Here, however, the nodes of the bottom layer represent routers that want to send messages to each other, and the layers above them contain extra routers that simplify the routing procedure. A message sent by one bottom-layer router climbs the tree until it reaches the branch that leads to the destination router, and then it is sent down.

A fat tree. Each node represents a router, and each router has four ports. Nodes T1 – T12 reserve two ports each for connecting to servers.

This design is easy to implement but inefficient: the extra layers of routers add overhead, and routers at the top of the tree are prone to congestion. The fat-tree structure is also fragile, since the loss of a single router can cut off large regions of the tree.

Theoretically, the best alternative is a “flat” network, in which the routers connect directly to each other. Ideally, one should connect the routers randomly, to maximize the diversity of routes through the network. But this is impractical, because calculating ad hoc paths through a random network is computationally intensive, and randomly connecting routers leads to data centers criss-crossed with wires.

Twelve routers (T1 – T12) linked through a fat tree (left) and a flat network (right). Each router has four ports; routers T1 – T12 reserve two ports each for connections to servers.

In a paper we recently posted to arXiv, we describe the first ever scalable flat-network datacenter. We introduce a “quasi-random” network topology that preserves many of the benefits of random connection and a passive optical component we call a ShuffleBox, which makes it practical to cable a flat network. The resulting network design — which we call RNG, for resilient network graphs — is now used in AWS data centers and is the default for most new builds globally. It uses 69% fewer routers, delivers up to 33% better throughput, and projects a 40% reduction in network equipment electricity consumption.

The secret of randomness

In the early 1990s, mathematicians showed that the optimal network for routing has a random topology, in which each router simply connects randomly to a few others. This is quite counterintuitive, but the overall network ends up having lots of different paths between all pairs of routers. Random networks also demonstrate excellent resilience, since no single router is more important than any other. The loss of 1% of routers results in a roughly 1% capacity loss. Degradation is proportional and predictable rather than catastrophic and concentrated.

From left to right: Ratul Mahajan, Giacomo Bernardi, and Seshadhri Comandur at the Amazon Web Services Networking Lab in Cupertino, CA, in front a of a server rack that includes ShuffleBoxes.

Networking researchers have also validated these results through simulations, showing that random, flat topologies achieve better performance than the corresponding fat trees.

But these results couldn’t make it in the real world. Any network design comes with a “routing protocol” that decides how packets reach their destinations. In a random network, computing and implementing the right set of routing paths can take a lot of hardware resources — well beyond what is present in commodity routers. On the other hand, using dedicated hardware for routing would be cost prohibitive. An even bigger problem is that cabling routers randomly in a datacenter is completely infeasible.

Our solution is to build a “quasi-random” network topology that has exactly the right mix of random and deterministic components.

Routing without structure

In a fat tree, the hierarchy itself tells packets where to go. And the paths generated are guaranteed to be the shortest possible. In a quasi-random graph, there is no obvious structure to exploit. Standard approaches to multipath routing in flat topologies typically require 20 to 80 times more memory than commodity hardware is equipped with.

Our key insight is that we can exploit the random structure of the topology to open up a wide range of path options in a lightweight manner.

Our routing algorithm, Spraypoint, has two components. The source router “sprays” its traffic randomly to all of its neighbors. Every (destination) router has some designated “waypoints” that feed traffic to it. The main scheme is that each data packet sent from the source goes to a random neighbor, after which the classic shortest-path algorithm routes it to a waypoint, and the waypoints feed it to the destination. The utility of spraying is that traffic can take a wide variety of paths to the destination, while the waypoints prevent traffic from congesting near the destination. In the implementation, we create various “rings” around each destination, and traffic is guided from each ring to a closer ring.

A sample network using our routing protocol. The destination router (t) is in orange; the ring of waypoints (wi) is in yellow; and the blue and grey nodes constitute the inner (ri) and outer (oi) rings, respectively.

By spraying to neighbors, Spraypoint provides nearly twice as many independent paths between routers as standard shortest-path routing techniques. This improves the likelihood that traffic will be routed around congested pathways or failed routers.

Making quasi-random cabling practical

A random graph connects arbitrary pairs of routers that may sit in different rooms, hundreds of meters apart. This is the strength of the topology, since it allows for fast communication between routers. But that is also its drawback, since cabling such a structure is extremely complicated.

This is where our quasi-random solution comes in. Instead of all connections being random, we fix specific parts of the network topology. Our central innovation is a passive optical device called a ShuffleBox. It has router-facing ports on one side and connects to other ShuffleBoxes on the other side. The internal wires are shuffled according to a special pattern, so that random connections between the ShuffleBoxes lead to an overall quasi-random topology.

Three server rooms (dashed squares), each with two ShuffleBoxes (trapezoids). One side of each ShuffleBoxes connects to servers (yellow circles); on the other side, ShuffleBoxes connect only to each other.

When a new rack arrives, a technician plugs its router into an available port on the local ShuffleBox. No rewiring elsewhere. The physical-cabling complexity, the number of cable runs, and the installation process are on par with those of a fat tree, even though the logical topology is quasi-random.

Predicting performance before construction

With any new network topology, operators need confidence that it will meet capacity and performance requirements before they commit to construction. Fat-tree topologies come with simple, well-defined models that predict performance and capacity constraints.

No equivalent existed for quasi-random graphs. We developed new mathematical models for various network statistics, such as path lengths, the number of routes, and how much traffic will end up on a particular link. These models give precise formulas that network operators can use to choose design parameters. We validated those models extensively, using 530 processor-years of simulation, the equivalent of running a single CPU for half a millennium, executed on Amazon EC2.

An operator can now specify a server count and a target performance level, compute the cheapest compliant topology, and be confident that it will work.

From theory to production

The first quasi-random network went live near Dublin, Ireland, at the end of 2024, carrying real production traffic. We validated performance against the mathematical predictions, identified operational refinements, and applied them in two additional deployments. In end-to-end benchmarks across these production fabrics, our flat topology matched fat-tree performance for multipath-transport workloads and latency-sensitive storage operations. No customer workload changes were required, and the network operates transparently beneath existing applications.

By April 2026, quasi-random wiring became the default architecture for most new AWS data centers globally. The 69% reduction in the number of routers translates directly into reduced power, cooling, and operational overhead at every site. For customers, it means more resilient infrastructure behind every API call, database query, and machine learning training job, without changing a single line of code.