this post was submitted on 23 Aug 2024
126 points (96.3% liked)
PC Gaming
8559 readers
534 users here now
For PC gaming news and discussion. PCGamingWiki
Rules:
- Be Respectful.
- No Spam or Porn.
- No Advertising.
- No Memes.
- No Tech Support.
- No questions about buying/building computers.
- No game suggestions, friend requests, surveys, or begging.
- No Let's Plays, streams, highlight reels/montages, random videos or shorts.
- No off-topic posts/comments, within reason.
- Use the original source, no clickbait titles, no duplicates. (Submissions should be from the original source if possible, unless from paywalled or non-english sources. If the title is clickbait or lacks context you may lightly edit the title.)
founded 1 year ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
It's not "because we're not fiddling" with anything.
It's because Windows' scheduler is objectively broken and not scheduling workloads correctly.
Can you elaborate? How is it breaking?
It assigns workloads to the virtual core (from SMT) before properly distributing them to other cores. Source
This is not an issue on Linux because they schedule threads correctly.
But I guess this post is about windows only doing some other branch prediction correctly on some admin mode, so I guess that way too.
Thanks for the explaination! I would have searched in but I'm on a phone and my kids are jumping on the couch/me. Have an upvote, on me.