- cross-posted to:
- linux_gaming@lemmy.ml
- cross-posted to:
- linux_gaming@lemmy.ml
You must log in or register to comment.
Fake news. It’s merely a re-send of the patches; nothing landed yet.
The Phoronix article and their title makes that clear; you editorialised it to state differently. (Also, that’s…cringe.)
(you)
Gaymers - NTSYNC Linux Patches lands To Help Boost Steam Play Gaming Performance
www.phoronix.com Magnolia_ to Linux@lemmy.mlEnglish ·
cross-posted to: linux_gaming@lemmy.worldlinux_gaming@lemmy.mlphoronix@lemmy.worldlinux_gaming@lemmit.onlineNTSYNC Linux Patches Revived To Help Boost Steam Play Gaming Performancewww.phoronix.com Body
Atemu @lemmy.ml
Fake news. It’s merely a re-send of the patches; nothing landed yet.
The Phoronix article and their title makes that clear; you editorialised it to state differently. (Also, that’s…cringe.)
That’s just an ACK and Elizabeth replied that she’ll resend again with further changes.
Nothing is in any tree that is going to Linus yet AFAICT.
We could be reasonably sure that it’ll go to Linus if it’s in char-misc but that hasn’t happened yet. I’m also actually not sure whether Greg’s or Arnd’s tree is the canonical one there.
Gaymers?
Better performance, but only for gay games, such as uh, well uh and um…
You might be able to read Arches faster.
678% performance gain is just crazy. I’d be interested in a comparison with native windows performance with these titles.
It was being compared to another implementation. Hers is actually better and can be fully implemented in Wine. It’ll be better but no one really knows the full concrete extend of improvement until it lands
It was being compared to another implementation.
I’m quite certain it was being compared to mainline WINE, so no esync or fsync which themselves usually double FPS in CPU-bound scenarios.
Hers is actually better
[citation needed]
From what I gather from the ntsync feedback thread where some users have tested the WIP patches, it’s not clearly better than esync/fsync but rather slightly worse. Though that isn’t very clear data as it’s still in development. Still, if it was very clearly better than the status quo, we should have already seen that.
can be fully implemented in Wine
It cannot, hence the kernel patch.
It’ll be better but no one really knows the full concrete extend of improvement until it lands
I see no reason to believe it should be “better”. If anything, I’d expect slightly worse performance than esync/fsync because upstream WINE primarily wants a correct solution while the out-of-tree esync/fsync patches trade some correctness for performance in games.
Ideally, I’d like to be proven wrong; that ntsync is both correct and performant but that’s not what you should expect going into this.
if it gets merged at all we won’t see it in proton till 2026 at this point. missed the boat for wine 10 I presume
