this post was submitted on 13 Nov 2023
1 points (100.0% liked)
Hardware
33 readers
1 users here now
A place for quality hardware news, reviews, and intelligent discussion.
founded 11 months ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
Damn.
Slimy as hell. Really bad move here. Hopefully every gamer channel provides similar coverage and a legion of 12th and 13th gen owners will become aware of this and really push back against this (as the gentleman in the video also hopes).
I know reviews mentioned some wonky stuff going on with E-core and P-core scheduling on 12th gen, when I purchased 12600k and 12700k for two machines for my home.
I'm feeling foolish for approaching this in good faith and assuming that Intel/Microsoft/game developers would continue to iterate on the issues and make software-based optimizations readily available.
If I had realized, I would have AMD systems right now.
It's a very poor decision on their part to roll out APO in this way. If I was compelled to upgrade from 12th gen for more performance, this APO mess guarantees that I move my platforms to AMD.
The example you chose is a terrible one, as for those that dont know that behavior is INTENDED by the Handbrake developers, This has been a known thing since Alder Lake's launch. The developers didnt ever want Handbrake to use 100% of your system, so its flagged as a low priority process so you can still use your PC without it being lagged out while encoding. So the scheduler sees that and will free up the P-cores when you put another window in focus, so you can use your system without lag, while the e-cores encode in the background.
If you go through the github you'll see the developers tell people they can override this manually, but the current implementation is exactly how its supposed to work.
You cant blame Thread Director or Windows scheduling for this specific case with Handbrake as its what the developers intended.