Gamers who use fsync are not going to see such a leap in performance in most games.
I don’t think that’s overlooked at all. 99.9% of people using WINE/Proton aren’t going to have any idea what fsync is, and almost nobody not using proton-cachyos is going to use it. fsync, itself a workaround, is niche within what’s already a niche.
Fsync maybe not but AFAIK esync is widely used. On some protondb pages there’s a hint to disable esync, not the other way round. And while esync is not as performant as fsync, it is still much better than vanilla
It’s worth noting that the new sync implementation shouldn’t cause any of the compatibility problems esync and fsync ran into, so it’s a worthwhile upgrade from a stability viewpoint even if a user won’t see huge performance gains.
i use ntsync whenever i can, but i’ve only had linux (cachyos) on my gaming rig since like august. that said, i believe one of their recent updates made ntsync the default for proton-cachyos
I don’t think that’s overlooked at all. 99.9% of people using WINE/Proton aren’t going to have any idea what fsync is, and almost nobody not using
proton-cachyosis going to use it. fsync, itself a workaround, is niche within what’s already a niche.Fsync maybe not but AFAIK esync is widely used. On some protondb pages there’s a hint to disable esync, not the other way round. And while esync is not as performant as fsync, it is still much better than vanilla
It’s worth noting that the new sync implementation shouldn’t cause any of the compatibility problems esync and fsync ran into, so it’s a worthwhile upgrade from a stability viewpoint even if a user won’t see huge performance gains.
i use ntsync whenever i can, but i’ve only had linux (cachyos) on my gaming rig since like august. that said, i believe one of their recent updates made ntsync the default for proton-cachyos