- cross-posted to:
- linux_gaming@lemmy.world
- cross-posted to:
- linux_gaming@lemmy.world
Funny, I just saw an article saying don’t get too excited about Linux gaming boosts because apparently Wine doesn’t use ntsync yet, and Valve already worked around ntsync by implementing the faster fsync in SteamOS.
esync = alpha version
fsync = beta version
ntsync = final release
Ntsync got rid of performance degradation that can occur with some games under esync and fsync and that’s the why it’s allowed to go in the mainline kernel, it has no downside.
Ntsync got rid of performance degradation that can occur with some games under esync and fsync
This explains SO MUCH! I was getting frustrated when games start out perfectly fine than 30 minutes in frames would drop significantly.
I believe that NTsync delivers better compatibility. I do not remember the details but Fsync can cause problems sometimes. So this is more like performance without compromise.
Now that it is in the kernel, I would expect Wine to move to it and for Proton to follow suit.
One less hack to maintain.
fsync isn’t faster than ntsync, it’s merely a workaround to match Linux to Windows synchronization primitives. From ntsync’s official description:
It exists because implementation in user-space, using existing tools, cannot match Windows performance while offering accurate semantics.
So without this, you either have a huge perfomance hit in case of an accurate implementation or you have good performance, but might run into edge cases where software doesn’t work well or at all because it’s not accurate (see https://github.com/ValveSoftware/Proton/issues/2922 for examples)
not my words. It’s the Valve dev who said it.
Why is he using the term “SteamOS kernel”?
Well, he’s talking about the kernel they are using in SteamOS. The Deck OS is also being extended to other handhelds.
Still a weird way to say this.
Gayming