• Jure Repinc@lemmy.ml
    link
    fedilink
    English
    arrow-up
    0
    ·
    3 months ago

    Or they just found out that Windows process scheduler is still broken beyond repair. If you look at the benchmarks on GNU/Linux performance is all there. For example see Phoronix benchmark

  • conciselyverbose@sh.itjust.works
    link
    fedilink
    English
    arrow-up
    0
    ·
    3 months ago

    During the course of our testing, we observed that Windows 11 was scheduling workloads on the 9700X in a manner that would try to saturate a single core first, by placing workloads on each of its logical threads.

    🤦‍♀️

    • adarza@lemmy.ca
      link
      fedilink
      English
      arrow-up
      0
      ·
      3 months ago

      so, basically, the os isn’t tuned for the new chips yet.

      the 2nd threads on smt-enabled cores are supposed to get hit last.

      • barsoap@lemm.ee
        link
        fedilink
        English
        arrow-up
        0
        ·
        edit-2
        3 months ago

        For values of “new chips” that include 20 year old ones. Foster was released 2001, the chips were single-core but you could have up to eight on a board so it’s still multi-core SMT. First on-die multi-core SMT seemed to have been Paxville, 2005.

        Or maybe Windows server has a proper scheduler and they never bothered bringing it to desktops?

      • SomeoneSomewhere@lemmy.nz
        link
        fedilink
        English
        arrow-up
        0
        ·
        3 months ago

        There should be no need for tuning, tweaking, or optimizing on functionality this basic.

        If you ask the processor, it will spit out a graph like this telling you what threads/cores share resources, all the way up to (on large or server platforms) some RAM or PCIe slots being closer to certain groups of cores.

  • schizo@forum.uncomfortable.business
    link
    fedilink
    English
    arrow-up
    0
    ·
    3 months ago

    This is shockingly stupid. SMT has been a thing on x86 long enough for it to be able to buy it’s own alcohol and yet somehow the windows scheduler STILL can’t fucking deal with it?

    I’m not a kernel-level developer or anything but I mean, at some point you have to wonder how fucking trash windows kernel internals are that this problem keeps happening over and over and over and…