As computation continues to move into the cloud, the computing platform of interest no longer resembles a pizza box or a refrigerator, but a warehouse full of computers. These new large datacenters are quite different from traditional hosting facilities of earlier times and cannot be viewed simply as a collection of co-located servers. Large portions of the hardware and so As computation continues to move into the cloud, the computing platform of interest no longer resembles a pizza box or a refrigerator, but a warehouse full of computers. These new large datacenters are quite different from traditional hosting facilities of earlier times and cannot be viewed simply as a collection of co-located servers. Large portions of the hardware and software resources in these facilities must work in concert to efficiently deliver good levels of Internet service performance, something that can only be achieved by a holistic approach to their design and deployment. In other words, we must treat the datacenter itself as one massive warehouse-scale computer (WSe. We describe the architecture of WSCs, the main factors influencing their design, operation, and cost structure, and the characteristics of their software base. We hope it will be useful to architects and programmers of today's WSCs, as well as those of future many-core platforms which may one day implement the equivalent of today's WSCs on a single board. Table of Contents: Introduction / Workloads and Software Infrastructure / Hardware Building Blocks / Datacenter Basics / Energy and Power Efficiency / Modeling Costs / Dealing with Failures and Repairs / Closing Remarks
The Datacenter as a Computer: An Introduction to the Design of Warehouse-Scale Machines
As computation continues to move into the cloud, the computing platform of interest no longer resembles a pizza box or a refrigerator, but a warehouse full of computers. These new large datacenters are quite different from traditional hosting facilities of earlier times and cannot be viewed simply as a collection of co-located servers. Large portions of the hardware and so As computation continues to move into the cloud, the computing platform of interest no longer resembles a pizza box or a refrigerator, but a warehouse full of computers. These new large datacenters are quite different from traditional hosting facilities of earlier times and cannot be viewed simply as a collection of co-located servers. Large portions of the hardware and software resources in these facilities must work in concert to efficiently deliver good levels of Internet service performance, something that can only be achieved by a holistic approach to their design and deployment. In other words, we must treat the datacenter itself as one massive warehouse-scale computer (WSe. We describe the architecture of WSCs, the main factors influencing their design, operation, and cost structure, and the characteristics of their software base. We hope it will be useful to architects and programmers of today's WSCs, as well as those of future many-core platforms which may one day implement the equivalent of today's WSCs on a single board. Table of Contents: Introduction / Workloads and Software Infrastructure / Hardware Building Blocks / Datacenter Basics / Energy and Power Efficiency / Modeling Costs / Dealing with Failures and Repairs / Closing Remarks
Compare
David Chou –
An awesome book explaining not only the physical side of the datacenter, but also the requirements of the software infrastructure that needs to be built on top for developers to efficiently leverage the datacenter resources. This book is a must read for any infrastructure engineer.
heidi –
I took my time to finish and truly understand the contents of this book because I was reading it for work. Our purpose was slightly different, which was to build a computational simulation server, much smaller than warehouse scale machines obviously. However I found this book very comprehensive, and perfect for beginners in parallel computing. It covers issues I didn't think of in the beginning of our project, such as heat generation and power supply (these are more relevant to hardware and I on I took my time to finish and truly understand the contents of this book because I was reading it for work. Our purpose was slightly different, which was to build a computational simulation server, much smaller than warehouse scale machines obviously. However I found this book very comprehensive, and perfect for beginners in parallel computing. It covers issues I didn't think of in the beginning of our project, such as heat generation and power supply (these are more relevant to hardware and I only know a bit of numerical computing). There are helpful "management" contents as well such as how to calculate ROI and Capex vs Opex. I totally recommend this book for any engineer who suddenly finds herself having to build a tiny "cluster" at work and have to start with googling shit up… That said, because this book is for beginners you'll need to start digging through the references listed at the back and read more from there.
Ralph N –
Good for beginners of parallel computing.
Trung –
Feels like a report paper (short and dense with statistics) than a book. There are a lot of insights into how Google operates, but it is a bit too short.
Wong Wen Hao –
Kevin Ferret –
Fred Dinkler –
Gareth Davis –
Christian Witts –
AG –
Miguel Angel –
Dexter –
Kevin –
Marc Donner –
D. Ramakrishnan –
Jeff –
Subhajit Das –
Chelsea –
Christopher Maxwell –
Roman Leventov –
Amin Khoshnood –
Nazmul Ahmed Noyon –
Jakob Thomsen –
Tine Hutchison –
Pyang –
Sebastien –
wszhou –
Federico Fregosi –
Kevin Li –
zlu –
Aaron Wolfson –
Adam Schepis –
Chris –
Mike Fisher –
James Waldrop –
Sean Keery –
David Yeo –
Rui Natário –
Nuno Guerreiro –
Victor –
Tim Cowlishaw –
Dan Winkler –
Andrew –
Mr. Tom –
MICHAEL RINGGAARD –
Bianca Gibson –
Chris –
Mike Murray –
S.yadhunandan –
Brad –
Anand Purohit –
Jeongho Park –
John –
Jake Schmidt –
Keegan –
Michael –
Marcin Kania –