this post was submitted on 23 Aug 2024
125 points (96.3% liked)

PC Gaming

8660 readers
451 users here now

For PC gaming news and discussion. PCGamingWiki

Rules:

  1. Be Respectful.
  2. No Spam or Porn.
  3. No Advertising.
  4. No Memes.
  5. No Tech Support.
  6. No questions about buying/building computers.
  7. No game suggestions, friend requests, surveys, or begging.
  8. No Let's Plays, streams, highlight reels/montages, random videos or shorts.
  9. No off-topic posts/comments, within reason.
  10. 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
[–] conciselyverbose 74 points 3 months ago (1 children)

It's not "because we're not fiddling" with anything.

It's because Windows' scheduler is objectively broken and not scheduling workloads correctly.

[–] [email protected] 3 points 3 months ago (1 children)

Can you elaborate? How is it breaking?

[–] conciselyverbose 13 points 3 months ago (1 children)

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.

[–] [email protected] 1 points 3 months ago

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.