Both Intel and AMD invented a methodology that can select the fastest core to be the 'favored core'. However, as with anything, Windows does not recognize that. Basically an application could end up... Windows 10 19H2 update to include Favored CPU Core Optimization
I was curious to find out which actual Intel CPUs would be positively affected by this update. The only CPUs that are applicable are these ones (found on Intel webpage, https://www.intel.co.uk/content/www/uk/en/support/articles/000021587/processors.html), that's because these are the only CPUs that support Intel® Turbo Boost Max Technology 3.0: Intel® Core™ i7-69xx/68xx Processor Family Intel® Core™ i9-7900X/i9-7920X/i9-7940X/i9-7960X/i9-7980XE/i7-7820X/i7-9800X Intel® Core™ i9-9820X/i9-99x0XE/i9-99x0X Intel® Xeon® Processor E5-1600 v4 Product Family (single-socket only)
On the mainstream CPUs you can just enable that setting in bios and all the cores will boost to maximum speed
Except, kind of the point is not all cores are equal. Some (especially in the case of AMD) can clock higher than others, even if you haven't overclocked.
Considering their track record lately should we start betting what they will break with this update on the first roll out ? I say they will break the power stager and will get one or more cores stuck to max speed even at idle ! Just guessing here
kind interesting if works correct but my Z170 board already boost all cores to same speed. now if some cores are weaker vs other cores at same speed i don't know. then again my 6700k isnt on the less of cpu it effect? if this being implemented in OS i don't see why it would be for new cpu's My bets are on they break the bank
There's something in some of the newer CPUs (with many many cores, the list of CPUs I gave above)...there's something in these CPUs that measures which cores are the strongest, and the other CPUs don't have that function. It then communicates to the OS which cores are the strongest, and then the scheduler distributes the work in the best way possible, that's my understanding. Yes, so that's what will happen with that update that this article is talking about. So it's not applicable to our 6700K's.
Intel already had software that did this in userspace as part of Turbo Boost 3.0 driver, its just more convenient (and presumably a bit less annoying) to get Windows to do it for you.
Would be nice,I would settle for the OS distributing the work more evenly among cpu cores, Hell I would settle for MS releasing updates that dont lead to mutlple headlines "Microsoft Win10 update breaking things and or causing issue"
theorically great, if it works, but frankly having to handle different core clocks AND voltages like on AMD is not something I'm looking for... it's also a very easy way to lie about performances, because 4.6Ghz boost for 2ms at idle is not 4.6Ghz, it's meaningless
The update is already rolled out, all that will be coming is an "enable" patch which turns on the features that are present already.
I am curious how it will turn out but that does seem to be the case between 18362 and 18363 where for the latest cumulative update (The .387 one.) a comparison shows that the only component that differs is that enablement package for 1909's build number. But then there's 18362.1022 as well for the insider slow ring for 19H2 which last I heard could be updated to from 18362.387 so if that has newer components still then there's a chance there's at least one more cumulative before these are all identical. Regardless most of 18363 / 1909 / Windows 10 19H2 is in place by this point just not enabled for non-insiders. Or if I misread then there's nothing and that applied to the previous update instead and there's just a small cumulative for .1022 if so and that will be brought up to the rest of these builds once 1909 is out either later this week or for patch Tuesday next week perhaps if Microsoft is timing it together with the regular monthly update rollout.
So the bomb is planted already and we wait for detonation? God help us all ! ((Obviously i am am mostly jocking although their track record with the last years updates is at the very least ....dodgy))