These articles are very misleading because Proton is already patched to include fsync (I think it’s fsync). So basically there won’t be any performance improvement for most games under 99.999% of setups. Still a good thing that this is merged because it means the regular wine outside of proton will now be on par with proton
I think there are situations that fsync does not cover very efficiently, to the point that it can cause timing issues that lead to some bugs / incompatibilities. The timing issues might be rare, but that doesn’t mean the overall efficiency is the same. It would be interesting to see benchmarks of fsync vs ntsync.
Of course, but the articles make it seem like it will 6x the performance in some games when in reality it won’t because the performance gain is already factored in upstream proton
hope it gets into wine staging soon
When will it hit arch linux?
I’ll probably release on March, since there’s a release every 2 months and 6.13 was on Jan 20th.
Holy shit, I thought that it would bring some minor improvements, but those benchmarks are insane
For some reason benchmarks won’t load on my device.
Could anyone please upload the images somewhere else?
The benchmarks are against vanilla Wine. A lot of people are using the fsync patches, so ntsync is more about accuracy - things that didn’t work under fsync should work under ntsync.
Instead of choosing between accuracy and performance hacks, ntsync should do it properly.
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.
