2.3: Cluster as a Single Computer- The Datacenter is the Computer

Introduction to Cloud Computing · LibreTexts

0%

Contents

    Text

    Size
    100%
    Theme
    Typeface
    Line length
    Spacing

    From LibreTexts, under CC BY 4.0, as the source states it; its equations are written in TeX, which the PDF shows typeset. This page at LibreTexts.

    2.3: Cluster as a Single Computer- The Datacenter is the Computer

    One of the most powerful concepts in large-scale computing is that a cluster of many machines can be made to act like one big machine [4]. In cluster computing, individual nodes are orchestrated to work in concert on computing tasks, achieving performance or reliability beyond the capability of any single computer. A cluster typically consists of commodity servers or PCs connected by a high-speed local network and managed by cluster middleware or a distributed operating system. To the end-user or application, the cluster can present a single system image – meaning the complexities of multiple machines are hidden, and the cluster is used as if it were one computer.

    On the hardware side, clusters leverage parallelism: tasks can be divided among nodes to work in parallel, dramatically speeding up processing for suitable workloads. Classic high-performance computing (HPC) clusters run tightly-coupled parallel programs using libraries like MPI (Message Passing Interface) to coordinate processes across nodes . In such cases, the cluster’s nodes may act almost like the cores of one giant supercomputer, exchanging messages with low-latency interconnects. Other cluster workloads might be more loosely coupled, such as independent web server instances handling different requests – here the cluster provides scalability by load-balancing requests over many nodes, appearing as one large web server to clients.

    A modern perspective on treating a cluster as one computer is encapsulated in the term “warehouse-scale computer” (WSC). The WSC approach is holistic – rather than viewing a data center as just a bunch of servers in a room, it’s designed and optimized as a unit. This enables engineering choices that consider system-level trade-offs: e.g. replicating data across racks to handle node failures, or scheduling tasks based on global load and thermal conditions.
    Cloud Datacenter consumption. Details in caption.

    Figure \(\PageIndex{1}\): Cloud data centers scale up from individual servers to racks of 42, to clusters of thousands — totaling up to 200,000 servers that use enough electricity to power a small city. This scale is needed to meet global demand, provide backup copies of data, and keep costs low. (CC BY 4.0; Felix Amoruwa) Access to a detailed description of Figure \(\PageIndex{1}\)

    Figure 2.3.1 depicts an example of datacenter hardware scale.

    Fault tolerance and high availability are fundamental advantages of clustering computers. In a well-designed cluster, if one node crashes or becomes unavailable, its tasks can be taken over by other nodes, allowing the overall system to continue functioning with minimal disruption. This is very different from a single-server system where one hardware failure could bring down the entire service. Clusters achieve this through redundancy and distributed protocols. For instance, data may be stored redundantly on multiple nodes via distributed file systems or RAID configurations so that “even if a single node fails, the network continues to function and data is backed up in multiple places” . Similarly, services can be replicated: if one server instance fails, a load balancer can route requests to a healthy instance. Many cloud systems go further by automating failure recovery – monitoring node health and automatically restarting failed components on other nodes. This yields highly available services where users may not even notice if behind the scenes a node was lost. In cluster terms, “high availability” clusters can seamlessly transfer work from a failed node to others, and “load-balancing” clusters distribute work evenly to avoid any single node overloading.

    Another aspect of treating a cluster as one system is resource sharing. The combined resources of the cluster – CPU cores, memory, disk, network bandwidth – can be allocated to different tasks as needed. Large enterprises often run mixed workloads on a cluster (some CPU-intensive, some memory-intensive, etc.) to utilize all parts of the machine efficiently. The cluster’s software layer can schedule jobs such that resources are shared fairly or efficiently among users. For example, one job might use 30% of the cluster’s CPU, another uses 50%, etc., with scheduling algorithms deciding placement. This is analogous to an operating system scheduler sharing CPU time among processes on a single computer, but on a cluster scale. Modern cluster managers exploit this to achieve very high utilization; in fact, Google has noted that intelligent cluster management saved them from having to build “several billion-dollar data centers” by avoiding low utilization and idle servers. The ability to pool resources is also called multi-tenancy in cloud settings – where different customers or services securely share the same physical cluster. Multi- tenancy is enabled by virtualization and containerization isolating each workload while the cluster OS (or orchestrator) allocates resources between them.

    In summary, cluster computing enables scale-out: increasing capacity by adding more nodes rather than making one node faster. It provides a path to practically unbounded computing power by aggregation. But to harness a cluster’s power effectively, sophisticated distributed system software is required. The next section discusses how such software manages and aligns workloads to the cluster’s resources – essentially acting as the “brain” of the cluster computer.


    This page titled 2.3: Cluster as a Single Computer- The Datacenter is the Computer was last modified on Tue, 22 Sep 2026 21:13:26 GMT and is shared under a CC BY 4.0 license and was authored, remixed, and/or curated by Felix Amoruwa.