4 ms·
The concerning part of this is that it sounds like they're only doing it because they accidentally gave a good feature to one of their cheaper parts, not for an
by josephcsible 5y ago
The concerning part of this is that it sounds like they're only doing it because they accidentally gave a good feature to one of their cheaper parts, not for any legitimate technical reason.
- PragmaticPulp 5y agoYou have to disable the efficiency cores to make it work, so it’s not exactly a net win unless you have some heavily AVX-512 workloads exclusively. The number of people who might benefit from this is extremely small. I’m guessing it’s more likely that they didn’t validate the chips for AVX-512 operation when selecting the thermal and power limits, and they’d really rather not have them coming back at higher warranty rates.
- teruakohatu 5y ago> they’d really rather not have them coming back at higher warranty rates. That would suggest that people are using them in enough quantities to warrent Intel "asking" for the functionality to be disabled.
- Wowfunhappy 5y ago> I’m guessing it’s more likely that they didn’t validate the chips for AVX-512 operation when selecting the thermal and power limits, and they’d really rather not have them coming back at higher warranty rates. These are K parts. They're built for overclocking. People are going to take them outside of their thermal and power limits anyway.
- _kulang 5y agoProbably an issue with scheduling P/E cores when they don’t support exactly the same instruction set
- benbenolson 5y agoAs with all things, AVX512 involves a tradeoff: core frequency can decrease when it's in use; if properly utilized, it can realize significant performance gains, but if not, can result in a reduction in performance. Don't be so quick to assume that a fence wasn't put up for a good reason.
- josephcsible 5y agoBut why not let the user make the choice? Why does Intel need to force it?
- Proven 5y ago