No idea on the loss side of things tbh, though given it's AI based, I'm assuming it can't be truly lossless

to use a toy example [...] for simple maths

I know, I just picked easy numbers for the sake of discussion. The actual data rate is not important to this particular discussion.

You obviously isn't aware of the sales statistics, AMD may win a tiny bit of marketshare when they are in the lead against Nvidia, but even when AMD was the clearly better cards and value, Nvidia maintained the bigger market share.

Compute units are significant, but so are the caches and i/o.

Real world datasets tend to have a lot of sparsity.

One of the biggest problems is called a page fault. Which is basically when the app needs to go to storage to find data to continue execution. This results in the processor waiting, which isn't free.

Generally, I'd say they go hand in hand about 50/50 plus or minus 10%.

One benchmarks can fit in L1 cache and really stress the cores but most benchmarks you're using all the levels of cache, ram, IO, etc... which is a hell of a lot compared to just a little bit of processor in that chip. GPUs again are often just massive collaborations of massive throughout and compute. So it can be to really separate.

And legit. Most data is compressed these days on the Internet. So that's again compute used to save data in flight. It's a neverending tradeoff.

This has nothing to do with creating textures. It's a texture compression algorithm.