数据中心计算机设计入门：仓库规模机器设计介绍

需积分: 10 51 浏览量更新于2024-07-19 1 收藏 11.33MB PDF 举报

DC-Computer-(an introduction to the design of warehouse-scale machines) 这本书籍《The Datacenter as a Computer》探讨了仓库规模机器（Warehouse-Scale Machines）的设计理念。以下是从标题、描述、标签和部分内容中总结出的重要知识点： 1. 仓库规模机器（Warehouse-Scale Machines）是一种大规模计算系统，旨在满足大数据处理和存储的需求。本书籍提供了对仓库规模机器的设计理念和架构的深入介绍。 2. 在《The Datacenter as a Computer》中，作者 Luiz André Barroso、Jimmy Clidaras 和 Urs Hölzle 从计算机架构的角度探讨了仓库规模机器的设计理念，涵盖了硬件、软件和系统架构等方面。 3. 仓库规模机器的设计需要考虑到可扩展性、可靠性、能效和成本等多个方面。作者们详细介绍了这些方面的设计理念和实践经验。 4. 本书籍还探讨了仓库规模机器在数据中心中的应用，包括数据存储、数据处理和网络架构等方面的设计理念和解决方案。 5. Synthesis Lectures on Computer Architecture 是一个系列丛书，旨在探讨计算机架构的科学和艺术。该丛书涵盖了计算机架构的各个方面，包括处理器架构、存储器架构、输入/输出系统、操作系统等。 6. Mark D. Hill 是该丛书的编辑，来自威斯康星大学麦迪逊分校。他是一位经验丰富的计算机架构专家，对计算机架构的设计和发展有深入的理解和见解。 7. 仓库规模机器的设计需要考虑到可扩展性、可靠性、能效和成本等多个方面。作者们详细介绍了这些方面的设计理念和实践经验。 8. 《The Datacenter as a Computer》第二版中，作者们还探讨了仓库规模机器在云计算和大数据时代的应用前景和挑战，包括数据中心的架构设计、资源管理和能效优化等方面。 9. 该书籍还探讨了仓库规模机器的安全性和可靠性问题，包括数据加密、身份验证和访问控制等方面的设计理念和解决方案。 10. 《The Datacenter as a Computer》是计算机架构和数据中心设计领域的经典著作，提供了宝贵的设计理念和实践经验，对计算机架构和数据中心设计领域的学生和专业人士具有重要的参考价值。

CHAPTER 1

Introduction

e ARPANET is over 40 years old, and the World Wide Web has recently celebrated its 20th

anniversary. Yet the Internet technologies that were largely sparked by these two remarkable mile-

stones continue to transform industries and our culture today and show no signs of slowing down.

e emergence of such popular Internet services as Web-based email, search and social networks,

plus the increased worldwide availability of high-speed connectivity have accelerated a trend toward

server-side or “cloud” computing.

Increasingly, computing and storage are moving from PC-like clients to smaller, often mobile

devices, combined with large Internet services. While early Internet services were mostly informa-

tional, today many Web applications oer services that previously resided in the client, including

email, photo and video storage, and oce applications. e shift toward server-side computing is

driven not only by the need for user experience improvements, such as ease of management (no

conguration or backups needed) and ubiquity of access, but also by the advantages it oers to ven-

dors. Software as a service allows faster application development because it is simpler for software

vendors to make changes and improvements. Instead of updating many millions of clients (with a

myriad of peculiar hardware and software congurations), vendors need only coordinate improve-

ments and xes inside their datacenters and can restrict their hardware deployment to a few well-

tested congurations. Moreover, datacenter economics allow many application services to run at a

low cost per user. For example, servers may be shared among thousands of active users (and many

more inactive ones), resulting in better utilization. Similarly, the computation itself may become

cheaper in a shared service (e.g., an email attachment received by multiple users can be stored once

rather than many times). Finally, servers and storage in a datacenter can be easier to manage than

the desktop or laptop equivalent because they are under control of a single, knowledgeable entity.

Some workloads require so much computing capability that they are a more natural t for

a massive computing infrastructure than for client-side computing. Search services (Web, images,

etc.) are a prime example of this class of workloads, but applications such as language translation

can also run more eectively on large shared computing installations because of their reliance on

massive-scale language models.

e trend toward server-side computing and the exploding popularity of Internet services

has created a new class of computing systems that we have named warehouse-scale computers, or

WSCs. e name is meant to call attention to the most distinguishing feature of these machines:

the massive scale of their software infrastructure, data repositories, and hardware platform. is

perspective is a departure from a view of the computing problem that implicitly assumes a model

2 1. INTRODUCTION

where one program runs in a single machine. In warehouse-scale computing, the program is an

Internet service, which may consist of tens or more individual programs that interact to implement

complex end-user services such as email, search, or maps. ese programs might be implemented

and maintained by dierent teams of engineers, perhaps even across organizational, geographic, and

company boundaries (e.g., as is the case with mashups).

e computing platform required to run such large-scale services bears little resemblance

to a pizza-box server or even the refrigerator-sized high-end multiprocessors that reigned in the

last decade. e hardware for such a platform consists of thousands of individual computing nodes

with their corresponding networking and storage subsystems, power distribution and conditioning

equipment, and extensive cooling systems. e enclosure for these systems is in fact a building,

which is often indistinguishable from a large warehouse.

1.1 WAREHOUSESCALE COMPUTERS

Had scale been the only distinguishing feature of these systems we might simply refer to them as

datacenters. Datacenters are buildings where multiple servers and communication gear are co-lo-

cated because of their common environmental requirements and physical security needs, and for

ease of maintenance. In that sense, a WSC is a type of datacenter. Traditional datacenters, however,

typically host a large number of relatively small- or medium-sized applications, each running on

a dedicated hardware infrastructure that is de-coupled and protected from other systems in the

same facility. ose datacenters host hardware and software for multiple organizational units or

even dierent companies. Dierent computing systems within such a datacenter often have little

in common in terms of hardware, software, or maintenance infrastructure, and tend not to commu-

nicate with each other at all.

WSCs currently power the services oered by companies such as Google, Amazon, Face-

book, and Microsoft’s online services division. ey dier signicantly from traditional datacenters:

they belong to a single organization, use a relatively homogeneous hardware and system software

platform, and share a common systems management layer. Often, much of the application, middle-

ware, and system software is built in-house compared to the predominance of third-party software

running in conventional datacenters. Most importantly, WSCs run a smaller number of very large

applications (or Internet services), and the common resource management infrastructure allows

signicant deployment exibility.

e requirements of homogeneity, single-organization control,

and enhanced focus on cost eciency motivate designers to take new approaches in constructing

and operating these systems.

Arguably, public clouds, such as Amazon Web Services or Google Cloud Engine, run many small applications,

like a regular datacenter. However, as seen by the provider, all of these applications are identical VMs, and they

access large, common services for block or database storage, load balancing, etc.

剩余155页未读，继续阅读

peter_wwhe

粉丝: 2
资源: 14

数据中心计算机设计入门：仓库规模机器设计介绍

Processor Microarchitecture_An Implementation Perspective

Please write a warehouse management system in python, thank you

Write a warehouse management app in python

WARN tool.BaseSqoopTool: Setting your password on the command-line is insecure. Consider using -P instead. --autoreset-to-one-mapper and --split-by cannot be used together.

./tpcc.lua --mysql-host=0.0.0.0 --mysql-user=root --mysql-password=123456 --mysql-db=tpcc prepare会加载多少warehouse

关于基于STM32单片机的货物抓取机器人的外文参考文献

最新资源