2022 Cloud Report (opens in new tab)

Dang! I didn't know this was a thing! Thanks!!

so? this isnt about accessibility its about preference. i prefer white backgrounds but im not sad when a site author chooses pink.

> I can't fathom what goes into the mind of a designer

Don't underestimate the damage an overly eager and naive developer can do.

Or, (maybe more likely in this case?) a CMS author who's been given a little bit too much power?

Shouldn't the web browser be the one implementing css rules?

"we" meaning you are an author on the report, or just at your job?

we need a fab competition as well. too many fabless like AMD, Apple...etc. deepened on TSMC

ASML deserves mentioning as well.

Hopefully some serious competition and general normality will return to consumer discrete GPUs sometime soon, too.

So the novel ("novel") idea that M1 is bringing is using high bandwidth LPDDR5 for desktop CPU memory, where it's currently typically used only for mobile CPUs. [1] Intel and AMD CPUs technically support LPDDRx, but no manufacturer exploits this for some reason. [2]

[1]: https://www.bgr.in/top-products/best-phones-with-lpddr5-ram-...

[2]: See other thread. :)

The memory in an M1 is not "on die" it is plain old DRAM that they buy from the Koreans and solder to the board just like Intel and AMD and everyone else. DRAM is made on a fundamentally different semiconductor process and there will never, ever be a CPU with on-die DRAM. DRAM that can be made on a CPU logic process is called eDRAM. A huge eDRAM is a few tens of megabytes, while a huge DRAM is gigabytes. The bit cell density of eDRAM is slightly better than SRAM and 1000x lower than DRAM.

All this makes me wonder where the Crystalwell concept could have gone if Intel had really stuck it out.

Agreed, in it's heyday (before Intel dominated in PC era), AMD was my go-to for performance processors.

Alder Lake and zen 3 are on comparable processes. Intel 10nm, now renamed Intel 7, has pretty much the same density as tsmc 7nm.

I think Intel stands to regain some lost ground over the next year or two, but Alder Lake isn't a compelling argument in a datacenter-focused discussion.

Alder Lake relies on brute force, inefficient power consumption to regain the performance crown. AMD's chips are much more efficient, and efficiency matters in datacenters. There is only so much power and cooling available to each rack unit.

I think Sapphire Rapids holds a lot of promise, but it remains to be seen.

Take a note, that node sizes of different factories aren't comparable, because they are measured quite differently. You can only compare TSMC v TSMC, Intel v Intel etc.

if by "enhance the distance" you mean Intel will fall farther in terms of price and performance to AMD, you're probably right.

> it is a fair assumption that their service offerings have been used by a significant amount of enterprises.

AWS revenue is 62B. Azure Cloud revenue is 23B. GCS revenue is 22B. I'd say that at 42% of the market, other cloud provider service offerings cumulatively are used by a significant amount of enterprises as well. These revenue numbers are probably artificially deflated due to the land war going on between these business units (i.e. Azure/GCS have to offer larger discounts to steal business from AWS) so it's hard to actually compare without deeper analytics access into these providers. Regardless, even individually these are massive revenue numbers indicating there's plenty of deployments on each of the clouds. Also, the "nobody got fired for IBM" reasoning is pretty flawed in tech; it's kind of ridiculous how often this argument is made.

Just to preface this next bit. I'm not asking about scenarios like "I run all parts of my business on AWS" which could change the benefits towards AWS (vendors love lockin because it raises prices). I'm asking mainly about a greenfield project that is selecting between the clouds equally.

> Each cloud comes with unique service / API complexity and despite being managed services that experience does not translate 1:1 across clouds

AFAIK the vast majority of all of this has been thoroughly commoditized. Do you have anything specific that you see as an important product/feature that Amazon has that the other's don't?

> AWS IAM policies cannot be reused

Not relevant for new deployments & AWS IAM policies are famously overly complex resulting in security vulnerabilities due to misconfiguration, but sure. IAM policies are unique to each cloud provider.

> and there may be differences in availability, durability, feature set et al

Experientially it seems like Google has an advantage there - AWS seems to have more frequent and longer-lasting outages. I doubt durability has a major difference & feature sets tend to be fairly even between them (might matter for the long tail). Also, that statement feels kind of empty as all it says is that there "may be" differences without stating any or which provider might come out ahead.

We need a browser extension to delete these stupid cookie consent popups

I read this as a strategic move. As their main goal is to get your name, company, title and email to download the report. So they were showing you snippets of interesting charts and then quickly covering it up.

I guess they make the information on the site unusable to obtain your work e-mail for downloading the pdf.

I'm not sure that is accurate for Gravaton3, which appears to be besting intel/amd in a number of cases. So, it doesn't appear there is a clear leader between the amd, intel and gravaton instances. Meaning everyone should be benchmarking their application and picking one.

https://www.phoronix.com/scan.php?page=article&item=graviton...

Amazon here seems to be leading the Arm technology pack, as they are using a newer generation of CPU, while arm instances on other providers tend to be providing gravaton2 (Neoverse-N1) based instances. I would imagine that gradually changing in the near future as those vendors also upgrade.

Graviton3 on AWS is better for most applications on a cost/performance basis, and in some cases also on straight latency.

Honeycomb has some great blogs about it: https://www.honeycomb.io/blog/present-future-arm-aws-gravito...

The big savings on graviton come from no hyperthreading. A VCPU on x86 is a hypercore, but a VCPU on graviton is a full core. So you get a full core and its L1 and L2 all to yourself. Usually for cheaper than an x86 VCPU.

As far as I know most AWS services can be run on graviton instances.

It does supports ARM. It's a Go project so it should except if they do exotic things.

Not just highmem configs. You have to do any decent memory intensive workloads to be able to see difference. Memory Access Latencies are higher for AMD machines because of various reasons.

I'm curious what it is about the name Cockroach that turns you off. I assume the name is intended to give the impression that the DB is hard to kill.

Other globally consistent NewSQL DBs: Spanner, TiDB, Yugabyte, SingleStore

Partitioning for existing DBs: Citus for Postgres and Vitess for MySQL.

Snowflake apparently just started to target transactional workloads with UniStore.