Jupiter rising

Recommendations

Info

Arjun Singh, Joon Ong, Amit Agarwal, Glen Anderson, Ashby Armistead, Roy Bannon, Seb Boving, Gaurav Desai, Bob Felderman, Paulie Germano, Anand Kanagala, Jeff Provost, Jason Simmons, Eiichi Tanda, Jim Wanderer, Urs Hölzle, Stephen Stuart, and Amin Vahdat On behalf of several teams in Google: Platforms Networking Hardware and Software Development, Platforms SQA, Mechanical Engineering, Cluster Engineering, NetOps, Global Infrastructure Group (GIG), and SRE.
Grand challenge for datacenter networks • Tens of thousands of servers interconnected in clusters • Islands of bandwidth a key bottleneck for Google a decade ago ■ Engineers struggled to optimize for b/w locality ■ Stranded compute/memory resources ■ Hindered app scaling 1 Mbps / machine within datacenter 3 Datacenter 1 Gbps / machine within rack 100 Mbps / machine within small cluster
Page 1: Jupiter rising: A decade of Clos to
Page 5 and 6: Motivation • Traditional network
Page 7 and 8: SDN: The early days • Control opt
Page 9 and 10: Outline • Motivation • Network
Page 11 and 12: Bisection b/w (bps) 2004 State of t
Page 13 and 14: Five generations of Clos for Google
Page 15 and 16: Challenges faced in building our ow
Page 17 and 18: (log scale) Bisection b/w (bps) 100
Page 21 and 22: Jupiter topology 21 + Scales out bu
Page 25 and 26: Network control and config New conv
Page 27 and 28: Challenges faced in building our ow
Page 29: Grand challenge for datacenter netw

Jupiter rising

Create successful ePaper yourself

Delete template?

Save as template?