Wine 11 rewrites how Linux runs Windows games at the kernel level, and the speed gains are massive
Wine 11 rewrites how Linux runs Windows games at the kernel level, and the speed gains are massive
What is often overlooked
Those benchmarks compare Wine NTSYNC against upstream vanilla Wine, which means there’s no fsync or esync either. Gamers who use fsync are not going to see such a leap in performance in most games.
Ntsync is great and there will be performance improvement. But not exactly massive
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.
From what I found online, Steam enables esync by default, and fsync if your kernel supports it.
Lutris has both options nowadays in the runner settings. Idk if they’re both enabled by default, but in my case they’re enabled. ymmv there.
From the article:
Futex2, often referred to interchangeably with fsync, did make it to Linux kernel 5.16 as futex_waitv, but the original implementation of fsync isn’t that. Fsync used futex_wait_multiple, and Futex2 used futex_waitv. Applications such as Lutris still refer to it as Fsync, though. It’s still kind of fsync, but it’s not the original fsync.
So since Jan 2022, it’s been in the stable Linux kernel. For Debian and its derivatives, it would be included beginning with Bookworm.
99.9% of people using WINE/Proton aren’t going to have any idea what fsync is
Speaking, although I’ve heard the term thrown around a lot. Can I get a layman’s overview?
You’re right, it is.
You can try all you want, but you will never get me to read the articles before commenting.