fallaciousBasis

No it’s not. That’s just the point at which a timer overflows which could cause a problem but it doesn’t guarantee one.

That’s not a thing.

At 49.7 days a timer overflows. That could cause problems… It doesn’t guarantee problems.

🚗🚗🚗🚗🚗🚗🚗🚗🚗🚗🚗🚗🚗🫠🫠🫠😶‍🌫️😶‍🌫️😶‍🌫️💀💀💀💢💢💢

You might want to check out morphe…

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.

Johnny 5 is alive!

Might want to check out morphe(Revanced might be dead?)

Nvidia has always had strong real time hardware accelerated memory compression.

Compute is basically a free lunch compared to memory bottlenecks. And individual textures will probably fit in low level caches, which allows the compute to flex.

So hyperbolic.

VHS was great, for its time. You can record over it again and again, like floppies. Crucially, they were cheap.

The biggest issue was your player. Shitty players liked to eat tapes.

That rewind noise then that sudden stop meant it was movie time! 🍿

No PTSD here. Just good memories.

So basically the system requirements of Chrome.

Oh that’s a fun one. Original incandescents lasted a very long time. Too long (over 10,000 hrs, and there are many examples of ones that have been lit for decades!). The various manufacturers actually conspired(spent a lot of money on research and development) to a 1,000 hr operational benchmark. Profits exploded.

This is common (engineered predictable fault.)