This is probably not a huge improvement for Steam gamers with Proton. I would like to see benchmarks on SteamOS using Proton.
With the provided benchmark results, its notable that they are comparing the new ntsync to the Wine version that has no alternative. Results are impressive. But on SteamOS and Steam in general, we have Proton, not base Wine. And Proton has something else already implemented, that improves performance. Its not as good as ntsync, but my point is, comparing the new implementation in Proton won’t be a huge difference like in the benchmark shown (as the benchmark is comparing Wine, not Proton).
I don’t think Proton has anything special going on in that regard actually. It’s got DXVK and all the other stuff built-in, but for the synchronization primitives I think it just uses fsync just like Wine does, so this might be interesting…
fsync isn’t part of wine, which is what they are referring to.
Fsync and Esync are both inaccurate representations and help in some places, while breakingnother things. Hence, while useful for games, they never got mainlined.
NTsync is an accurate reimplementation, hence why this functionality will finally become part of wine proper.
Yup. And it’ll be a huge improvement overall to simply have both performance and accuracy in one, and not have to pick one or the other, regardless of what application is being run.
This is probably not a huge improvement for Steam gamers with Proton. I would like to see benchmarks on SteamOS using Proton.
With the provided benchmark results, its notable that they are comparing the new ntsync to the Wine version that has no alternative. Results are impressive. But on SteamOS and Steam in general, we have Proton, not base Wine. And Proton has something else already implemented, that improves performance. Its not as good as ntsync, but my point is, comparing the new implementation in Proton won’t be a huge difference like in the benchmark shown (as the benchmark is comparing Wine, not Proton).
I don’t think Proton has anything special going on in that regard actually. It’s got DXVK and all the other stuff built-in, but for the synchronization primitives I think it just uses fsync just like Wine does, so this might be interesting…
fsync isn’t part of wine, which is what they are referring to.
Fsync and Esync are both inaccurate representations and help in some places, while breakingnother things. Hence, while useful for games, they never got mainlined.
NTsync is an accurate reimplementation, hence why this functionality will finally become part of wine proper.
I see. Either way there are some substantial improvements over fsync in some cases, so it should benefit Proton as well.
Yup. And it’ll be a huge improvement overall to simply have both performance and accuracy in one, and not have to pick one or the other, regardless of what application is being run.