Another Ntsync x Fsync comparison by me, enjoy.
How are the benchmarks differently limited? It looks like the same hw config each time
The Ratchet & Clank CPU Limited run has some noticeable FPS dips/loss under NTSYNC that FSYNC doesn’t have. It seems like NTSYNC generally trails or ties FSYNC in most other cases. I didn’t watch every minute of the footage - just skipped around through some of the CPU-limited sections since I imagine that’s the only part that matters. In any case, it seems like there’s not much to gain from using NTSYNC yet; maybe improvements will be made to at least tie FSYNC. My rudimentary (possibly incorrect) understanding is that FSYNC is hacky and that NTSYNC is the “correct” way to do it, so if nothing else getting NTSYNC to tie FSYNC means FSYNC can be deprecated at least.
It’s main benefit is compatibility. As you said fsync is a hack and can cause issues with some games and applications.
The other benefit is more about packaging and the like, in that you won’t have to deal with third party patches. Not an issue if you’re using Proton but can be if you’re using vanilla Wine.
just skipped around through some of the CPU-limited sections since I imagine that’s the only part that matters.
Yeah, pretty much, I included both for the sake of it.
In any case, it seems like there’s not much to gain from using NTSYNC yet; maybe improvements will be made to at least tie FSYNC. My rudimentary (possibly incorrect) understanding is that FSYNC is hacky and that NTSYNC is the “correct” way to do it, so if nothing else getting NTSYNC to tie FSYNC means FSYNC can be deprecated at least.
It might be better in the future, but it’s not there yet, the implementation is not even finished to be fair.
@CoyoteFacts @bargu the biggest issue … some distributions (cachyos for example) have such a new kernel which doesn’t support fsync ( winesync ) and you want to use the newest kernel for modern amd gpu’s ( eg.: 9070 xt) so downgrade to 6.11 ( last kernel with winesync ) is not a good choice.
Fsync hasn’t been dropped from the kernel, 6.15 still supports it, this test was done on 6.15.
He may want to say “fastsync” (whose kernel part called winesync). It’s the predecessor of NTsync and was renamed to NTsync when merged into linux mainline.
Before NTsync was merged, those distrobutions provides the kernel packages with winesync patches. Since linux 6.12, NTsync was merged so they droped winesync from kernel package. But NTsync’s API is different with fastsync/winesync, so old wine with fastsync support will stop working with new kernel. (While NTsync still isn’t merged to wine)
@Coelacanthus @bargu isn’t protons fallback esync if winesync isn’t available ? Wasn’t it esync -> winesync (fastsync) -> ntsync ?
