3 ms·
> Start time: Thu Oct 14 04:45:44 2021 UTC > End time: Mon Mar 21 04:16:52 2022 UTC > Total elapsed time: 157 days, 23 hours, 31 minutes and 7.651 seconds >
by alophawen 4y ago
> Start time: Thu Oct 14 04:45:44 2021 UTC
> End time: Mon Mar 21 04:16:52 2022 UTC
> Total elapsed time: 157 days, 23 hours, 31 minutes and 7.651 seconds
> Total storage size: 663 TB available, 515 TB used
> Total I/O: 43.5 PB read, 38.5 PB written, 82 PB total
Yea, but how much energy did you waste for 100T digits of crap, Google???
This was done thru a massive energy crisis, mind you.
- frankchn 4y agoThe main node has 64 physical cores and 1TB of RAM, and the 24 storage nodes have 8 cores and 16 GB of RAM (192 cores and 384GB of RAM total). So we are using 256 cores and 1.5 TB of RAM, so probably about 7.5 kW or so. Over 5 months, the compute would have used 27 MWh, so about the energy content of ~750 gallons of gas. The storage will obviously use more energy (I don't know if they are using spinning disks or SSDs), but I think ~50-100 MWh for the entire computation is a reasonable estimate.
- Youden 4y agoThey ran this in us-central1-c (Iowa) [0] which as of 2020 was 93% renewable [1]. The energy crisis mainly affects oil and coal prices in the US so I don't believe Google's renewable-powered computations should have any effect. If they'd run it in Germany where people are being asked to conserve electricity, things might be different. [0]: https://github.com/GoogleCloudPlatform/pi-delivery/blob/main/pi-100t/env.tf https://github.com/GoogleCloudPlatform/pi-delivery/blob/main... [1]: https://cloud.google.com/sustainability/region-carbon https://cloud.google.com/sustainability/region-carbon