Linux Benchmarks for Native Games

Graphics / Linux Linux
1

I’ve seen alot of benchmarks on phoronix about gaming, but its mostly AMD open source, or wine benchmarks. I yet to have seen benchmarks of native OpenGL and Vulkan benchmarks comparing Linux and Windows. I don’t know why, but I was always under the impression this was due to Linux being behind in gaming performance.

Now this isn’t a reason, for me at least, to stop using Linux and go back to Windows. I love Linux, and would never use Windows again, and use Linux as my desktop PC, and have been, for the past 5 years. With that said, I took the time to install Windows 10, and run some native games under each system to see who has better performance. The latest drivers are being used as of this post.

My specs are the following.

Core 2 Quad Q9650 @ 3.8GHz
GeForce 760 GTX
4GBs DDR2

Here are my results, and they are legit, I promise.

quakespasm - Linux: 1320 - Windows: 1240
ioquake3 - Linux: 509 - Windows: 512
vkquake - Linux: 993 - Windows: 950-996

These were simply timedemos. I used “timedemo demo1” for quakespasm and vkquake, and “demo four” for ioquake3.

Vulkan under windows was very inconsistant, but to my surprise, Linux is faster, or just about the same as Windows. I’ve seen so many videos about how Windows has better performance over Linux in gaming, but this simply isnt the case. For wine benchmarks sure, but native ports are just as fast, or FASTER.

I just wanted to personally thank all of you at NVIDIA, for maturing the Linux proprietary drivers, and be steps ahead of Intel and AMD in terms of performance, on Windows AND Linux.

No one can say anymore that Windows has better performance over Linux in gaming, its simply not true, and thats all because you guys put forth the effort in maturing the drivers.

Thank you guys, so much. Seriously, thank you.

Vincent Grande

PS:

I always wanted to thank Valve, for also maturing Linux gaming and them essentially being the reason I switched over to Linux. Thank you guys so much as well.

2

Awesome Reply,

Finally Years Later for me Using Ubuntu/Linux for 11 years, and hoping this “Game Changer” (pun Intended)

Linux by definition is faster than Windows on EVERY LEVEL but Windows keeps pushing their Proprietary SHITE to have inbedded buggy code that only they know how to deal with and Linux/Ubuntu and Mac alike have to reverse engineer these bus ex.s)

1/ ACPI Errors - Microsoft’s Fault!!
‣ https://en.wikipedia.org/wiki/Advanc...ower_Interface
∘ It’s suppose to be a standard that any operating system can properly implement. However, in typical Microsoft fashion, MS operating systems do not follow or properly implement the ACPI standard. Instead, MS gives motherboard manufacturers their own improperly implemented ACPI code for inclusion in the motherboard BIOS/UEFI. The code runs fine with MS windows but all for other operating systems like linux there can be problems. Because of MS’s market dominance, the faulty ACPI implementation from MS has become the de facto industry standard. As a result, linux and other non-MS operating systems have to reverse engineer the faulty ACPI implementation from MS. That’s why you can see problems in linux with ACPI related functionality like suspend to ram, hibernate, etc.
∘ Apparently, the ACPI related code in certain newer linux kernels has a problem with the typical BIOS/UEFI ACPI implementation on certain motherboards which is why we’re getting those error messages. Even though I get those error messages at the beginning of the boot process, I’ve had no problems with suspend/resume or any other ACPI related issues. Here’s another guy with the same problem so you are not alone:
‣ https://www.reddit.com/r/linux/comments/69rfh2/acpi_errors_on_any_linux_installation/
∘ The advice there was to not run in BIOS legacy mode by disabling UEFI but to run in UEFI mode instead with secure boot disabled. I haven’t bothered with it myself since I have several operating systems already installed with BIOS legacy mode and I would have to reinstall everything if I wanted to switch to UEFI mode.

2/ Updates to DirectX Always have INBEDDED errors built in.