Support us on Patreon: https://www.patreon.com/hardwareunboxedJoin us on Floatplane: https://www.floatplane.com/channel/HardwareUnboxedBuy relevant products ...
Intel’s E cores doing what they are supposed to on 2 games and 2 years after their debut, and only on their newest cpu lineup, peak Intel engineering right here
which just shows the scheduler is wrong. which people who cared to put the effort in already did manually with lasso. the only missing piece is random main kernel threads jumping on to p cores. AMD scheduler isn’t perfect either. And both companies are going big/little. so plenty of room to keep improving.
Thread Director doesn’t do any directing, it’s a a set of new registers the OS scheduler is supposed to read for feedback on how well a thread is running on a core. If APO can do it right, it means the scheduler is wrong.
15.6 HARDWARE FEEDBACK INTERFACE AND INTEL® THREAD DIRECTOR
Intel processors that enumerate CPUID.06H.0H:EAX.HW_FEEDBACK[bit 19] as 1 support Hardware Feedback
Interface (HFI). Hardware provides guidance to the Operating System (OS) scheduler to perform optimal workload
scheduling through a hardware feedback interface structure in memory.
More like peak Microsoft engineering, since this is something that was always supposed to be done by the operating system. Microsoft is so awful Intel had to do it themselves.
I mean unless you’re Apple and have full top to bottom control of your hardware and software stack it takes some time for software to catch up with the hardware.
Took a while for games to use MMX, SSE, AVX. Stuff that uses AVX512 can probably be counted on one hand.
Good ray traced games are becoming mainstream just now, two whole generations after GeForce 20 series.
I do begrudge Intel for holding this back from 12th and 13th gen users though.
Even Intel’s 1st iteration of MMX was a kludge, as it used the floating point unit, so you could either use FP, or MMX, but not both simultaneously o.O
Took awhile for that to be separated and gain the benefits of both available together.
Intel also added 57 new instructions specifically designed to manipulate and process video, audio, and graphical data more efficiently.
These instructions are oriented to the highly parallel and often repetitive sequences often found in multimedia operations.
Highly parallel refers to the fact that the same processing is done on many different data points, such as when modifying a graphic image.
The main drawbacks to MMX were that it only worked on integer values and used the floating-point unit for processing, meaning that time was lost when a shift to floating-point operations was necessary.
These drawbacks were corrected in the additions to MMX from Intel and AMD.
Intel’s E-cores + Thread Director work perfectly fine 98% of the time, but there are edge cases where the Windows Scheduler cant get it right, even with the hints from Thread Director, and that’s where APO comes in, to manually force the correct scheduling.
Also lets not pretend that AMD isnt suffering scheduling issues themselves, the 7950x3D and 7900x3D are shunned because they have WORSE scheduling in games as they rely on the Windows Scheduler to just try and figure things out itself, and that doesnt usually work with 2 CCD’s with one having a higher frequency and the other more cache.
Intel’s E cores doing what they are supposed to on 2 games and 2 years after their debut, and only on their newest cpu lineup, peak Intel engineering right here
which just shows the scheduler is wrong. which people who cared to put the effort in already did manually with lasso. the only missing piece is random main kernel threads jumping on to p cores. AMD scheduler isn’t perfect either. And both companies are going big/little. so plenty of room to keep improving.
correction: it shows that Intel Thread Director is wrong, and that the scheduler shouldn’t trust it.
Thread Director doesn’t do any directing, it’s a a set of new registers the OS scheduler is supposed to read for feedback on how well a thread is running on a core. If APO can do it right, it means the scheduler is wrong.
facepalm are you daft?
how the scheduler gets information from ITD doesn’t change what ITD does.
More like peak Microsoft engineering, since this is something that was always supposed to be done by the operating system. Microsoft is so awful Intel had to do it themselves.
I mean unless you’re Apple and have full top to bottom control of your hardware and software stack it takes some time for software to catch up with the hardware.
Took a while for games to use MMX, SSE, AVX. Stuff that uses AVX512 can probably be counted on one hand.
Good ray traced games are becoming mainstream just now, two whole generations after GeForce 20 series.
I do begrudge Intel for holding this back from 12th and 13th gen users though.
Even Intel’s 1st iteration of MMX was a kludge, as it used the floating point unit, so you could either use FP, or MMX, but not both simultaneously o.O
Took awhile for that to be separated and gain the benefits of both available together.
https://www.informit.com/articles/article.aspx?p=130978&seqNum=7
and they refuse to let people buy cpus without them, cant let amd win every bench mark that the vast majority of gamers will never use
It’s not even engineering. It’s a software lock. Absolute bonkers.
Screw intel as an owner of a 13700k
It’s the exact opposite of what you’re saying.
Intel’s E-cores + Thread Director work perfectly fine 98% of the time, but there are edge cases where the Windows Scheduler cant get it right, even with the hints from Thread Director, and that’s where APO comes in, to manually force the correct scheduling.
Also lets not pretend that AMD isnt suffering scheduling issues themselves, the 7950x3D and 7900x3D are shunned because they have WORSE scheduling in games as they rely on the Windows Scheduler to just try and figure things out itself, and that doesnt usually work with 2 CCD’s with one having a higher frequency and the other more cache.
Importantly, you think the fix will come for 12/13 gen Intel? You seem to know what you are talking about.
Fine wine baby! Oh, wrong company.