Path: ...!news.nobody.at!eternal-september.org!feeder3.eternal-september.org!news.eternal-september.org!.POSTED!not-for-mail From: Lawrence D'Oliveiro Newsgroups: comp.arch Subject: Re: architectural goals, Byte Addressability And Beyond Date: Tue, 4 Jun 2024 01:30:49 -0000 (UTC) Organization: A noiseless patient Spider Lines: 12 Message-ID: References: MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Injection-Date: Tue, 04 Jun 2024 03:30:50 +0200 (CEST) Injection-Info: dont-email.me; posting-host="d7d916175bb629e2353c22c0a9deb72e"; logging-data="140054"; mail-complaints-to="abuse@eternal-september.org"; posting-account="U2FsdGVkX1+bwZ9+F8v3L0Flb4OdkiuE" User-Agent: Pan/0.158 (Avdiivka; ) Cancel-Lock: sha1:gskPwbVfPqu6cIFG+zWPtrWC7RI= Bytes: 1796 On Sat, 1 Jun 2024 07:47:49 -0000 (UTC), Thomas Koenig wrote: > One of the main selling points [of zSeries] is the hardware > reliability ... Quite an expensive way to get reliability. How does an outfit like Google achieve essentially 0% downtime? By running a swarm of half a million commodity servers, that’s how. Every part has been built to the lowest cost, except the power supply. And they discovered they can run their data centres a little hot, to save on cooling costs, at the expense of a slightly higher failure rate. Because if a few thousand servers are down at any particular time, none of their users even notices.