Intel Thread Director bude upravljal sa svime pomalo u pozadini, ali prednost budu i dalje imale veće/jače jezgre, ne ide Alder Lake na 5.3GHz bez razloga, a Intel i dalje voli visoke taktove ...
Citiraj:
|
It’s important to understand that for the desktop processor with 8 P-cores and 8 E-cores, if there was a 16-thread workload then it will be scheduled across all 8 P-cores with 8 threads, then all 8 E-cores with the other 8 threads. This affords more performance than enabling the hyperthreads on the P-cores, and so software that compares thread-to-thread loading (such as the latest 3DMark CPU Profile test) may be testing something different compared to processors without E-cores.
|
Citiraj:
|
It all boils down to having the right functionality to help the operating system make decisions about where to put threads that require low latency vs threads that require high efficiency but are not time critical. So it’s easy enough (now) to tell an operating system that different types of cores exist. Each one can have a respective performance and efficiency rating, and the operating system can migrate threads around as required. However the difference between Windows 10 and Windows 11 is how much information is available to the scheduler about what is running.
|
Citiraj:
Intel classifies the performance levels on Alder Lake in the following order:- One thread per core on P-cores
- Only thread on E-cores
- SMT threads on P-cores
That means the system will load up one thread per P-core and all the E-cores before moving to the hyperthreads on the P-cores.
On top of this, Intel says that Thread Director can also optimize for frequency.
If a thread is limited in a way other than frequency, it can detect this and reduce frequency, voltage, and power.
|
Ništ, budemo pričekali službene recenzije da vidimo kak to sve skupa funkcionira.
