Intel's Hybrid Big Core Little Core strategy could be a disaster for Alder Lake

Lack of AVX512 isn't a big deal. It's just used for marketing nice benchmarks. It's really only useful for Data Center and HPC. How often are people running insanely floating point critical applications in the consumer space? Especially for a BIG.Little configuration designed for power efficiency over raw compute speed. If you need that much speed, using a GPU is significantly faster.

As for the other instructions, pretty sad Intel has to disable them to use those little cores. Mine as well not include them at that rate.

It's funny just the other day I read an article about how Linus Torvalds (Creator of Linux) was talking about how he wants AVX512 to die in consumer space.

Kinda got his wish :D
 
Last edited:
Lack of AVX512 isn't a big deal. It's just used for marketing nice benchmarks. It's really only useful for Data Center and HPC. How often are people running insanely floating point critical applications in the consumer space? Especially for a BIG.Little configuration designed for power efficiency over raw compute speed. If you need that much speed, using a GPU is significantly faster.

As for the other instructions, pretty sad Intel has to disable them to use those little cores. Mine as well not include them at that rate.

It's funny just the other day I read an article about how Linus Torvalds (Creator of Linux) was talking about how he wants AVX512 to die in consumer space.

Kinda got his wish :D

A big part of why AVX-512 is a disaster in the consumer space is because it isn't supported on mainstream desktop processors. Intel's 10nm woes have hit them hard. That's why it is basically HEDT/server only.

Ice Lake has AVX-512, and the instruction set it important to Intel's AI compute stuff. That said, Linus is right for the most part.

At OC3D, I've only known Tom to use AVX-512 as a stupidly hard OC test for compatible processors. Basically a power virus on the newer versions of Prime95. Get those thermals up to properly stress an OC.

If true, this Alder Lake stuff will make AVX-512 a bigger mess in the consumer market. It's crazy.
 
It is worth noting that a lot of newer AVX-512 extensions(Further modular extensions to the AVX-512 Foundation x86 extension) are still useful with 256 and 128-bit registers, and could be useful in place of older SSE or AVX/2 implementations that didn't require the actual 512-bit register aspect of AVX-512, and you won't get downclocking from using AVX-512 on these smaller register sizes.

Of course though no one is going to actually use it in these cases with all the fragmentation in support, not just amongst Intel tbf but across the x86 market. But yeah Linus also has a point that these gains aren't practically worth the transistor budget/cost of the units so there's no real reason for AMD to adopt yet, at least not while they're using the same dies across enterprise and consumer desktop.

Disabling FP16 hardware support isn't going to help with adoption there either.
 
Last edited:
Lack of AVX512 isn't a big deal. It's just used for marketing nice benchmarks. It's really only useful for Data Center and HPC. How often are people running insanely floating point critical applications in the consumer space? Especially for a BIG.Little configuration designed for power efficiency over raw compute speed. If you need that much speed, using a GPU is significantly faster.

As for the other instructions, pretty sad Intel has to disable them to use those little cores. Mine as well not include them at that rate.

It's funny just the other day I read an article about how Linus Torvalds (Creator of Linux) was talking about how he wants AVX512 to die in consumer space.

Kinda got his wish :D

Yeah I saw another article where hes said "Intel needs to stop making magical features no one cares about, and start fixing problems we have had from day 1"

He puts these new features down as Intels way to skew benchmarks in their favour as much as possible.
 
Yeah I saw another article where hes said "Intel needs to stop making magical features no one cares about, and start fixing problems we have had from day 1"

He puts these new features down as Intels way to skew benchmarks in their favour as much as possible.

Basically this. I took it as stop making fancy benchmarks instructions and actually fix your damn vulnerabilities! ^_^
 
Anen is all I wanted to say, but it says my message is to short. So howctonwrite more and say absolutely nothing can be done, I see that proved every day.
 
Back
Top