- Cloud Run: the latest iteration on the "serverless" concept, based on (Docker) containers; under the hood, Cloud Run is actually using Knative; the other serverless products are Cloud Function and App Engine. Cloud Run vs Cloud Functions vs App Engine
- API Gateway: still in beta but looks like a replacement for Cloud Endpoint. API Gateway vs Cloud Endpoint
- DataFlow vs Dataproc
From this article
Google found that the performance of its web search algorithm, the heart and soul of the company, scaled well with both the number of cores and the number of threads available to it. IBM's POWER9 processor is a many-core, many-thread beast. Variants of the chip range from 12 to 24 cores, with eight threads per core for the 12-core version and four threads per core for the 24-core version. Intel's chips support only two threads per core via hyperthreading.
They're not well suited for workloads that don't benefit from more threads, which is why the market-share ceiling for POWER isn't all that high.
I was blindly following the SDK installation guide (https://cloud.google.com/sdk/docs/install) until I got this error when running
E: Conflicting values set for option Signed-By regarding source https://packages.cloud.google.com/apt/ cloud-sdk: /usr/share/keyrings/cloud.google.gpg != E: The list of sources could not be read.
then I realized that some steps are "alternatives", so the keys were messed up. To fix this, remove the files and start over:
$ sudo rm /usr/share/keyrings/cloud.google.gpg $ sudo rm /usr/share/keyrings/cloud.google.gpg~ $ sudo rm /etc/apt/sources.list.d/google-cloud-sdk.list