| 17 Jul 2025 |
K900 | In reply to @woobilicious:matrix.org K900: your post mentions Intel-RT on non-x86, does that mean you can run Arc graphics on Arm? Always could | 04:54:28 |
K900 | They're just PCIe | 04:54:28 |
K900 | The RT code had some handrolled x86_64 SIMD but they got rid of that | 04:54:41 |
| ribosomerocker joined the room. | 23:58:21 |
| 18 Jul 2025 |
jonhermansen | Holy crap, I've really been missing out. Looking Glass performance is really good. Now if I can only figure out how to correctly isolate and pin my CPU cores... | 02:40:56 |
jonhermansen | Is anyone doing similar things and wanna share their setup? | 02:42:39 |
jonhermansen | I have serious problems with automatic core assignment in virt-manager with a game that is basically single core. Maybe I should simply try reducing the number (I have 16 P-Cores, so I gave 12 to the VM)
Maybe I also need hugepages
I thought KVM would be maybe 5% to 10% performance hit. The latency on the system becomes really bad and I don't know why. | 02:47:39 |
jonhermansen | * I have serious problems with automatic core assignment in virt-manager with a game that is basically single core. Maybe I should simply try reducing the number (I have 16 P-Cores, so I gave 12 cores to the VM)
Maybe I also need hugepages
I thought KVM would be maybe 5% to 10% performance hit. The latency on the system becomes really bad and I don't know why. | 02:49:17 |
jonhermansen | I have 144hz monitor and the latency transferring data from the GPU is very low, but I'm still trying to iron out the CPU issues in the guest.
Maybe I should switch to invoking qemu from a script or as a systemd service | 03:08:11 |
jonhermansen | * I have serious problems with automatic core assignment in virt-manager with a game that is basically single threaded. Maybe I should simply try reducing the number (I have 16 P-Cores, so I gave 12 cores to the VM)
Maybe I also need hugepages
I thought KVM would be maybe 5% to 10% performance hit. The latency on the system becomes really bad and I don't know why. | 03:10:08 |
jonhermansen | And for some reason, I can not use host-passthrough cpu or else the guest will crash. Even with migratable="off" | 03:10:55 |
jonhermansen | guest is Windows 10 | 03:11:42 |
| @haauler:matrix.org joined the room. | 14:24:28 |
| Gaëlle joined the room. | 14:47:56 |
colemickens | I feel so lost trying to keep track of FSR3/3.5/4, the new lossless scaling stuff, what exists in Proton/Gamescope/drivers. Ugh. | 23:27:53 |
colemickens | I do know Halo has like zero support for FSR so I guess I don't care about that for now. | 23:28:06 |
colemickens | So I guess I just care about whatever Proton has built-in or whatever I can get through Gamescope's upscaling if I choose to use it. | 23:28:25 |
colemickens | 🤔 | 23:28:29 |
| 19 Jul 2025 |
| Seong Yong-ju joined the room. | 04:56:14 |
K900 | In reply to @colemickens:matrix.org I feel so lost trying to keep track of FSR3/3.5/4, the new lossless scaling stuff, what exists in Proton/Gamescope/drivers. Ugh. Drivers are basically out of the picture for this | 05:46:44 |
K900 | On Linux at least, on Windows there's some driver side upscaling injection nonsense that could just be a Vulkan layer but D3D doesn't have those so lol | 05:47:52 |
woobilicious | You definitely need hugepages, that gives a 30% boost in performance on native factorio with a custom malloc lol, and find the correct CPU topo hints (try Epyc ones?), passthrough didn't work for me either. look at mem bloon driver too. | 06:51:55 |
woobilicious | I haven't used this config in like 3 years, but I got good performance with this on my 5600X: https://gist.github.com/YellowOnion/132f85ca3f81a7594fd9bcd1e424cc18 | 06:56:16 |
olivia | this is for the case where an application isn't built with FSR support? | 07:17:01 |
K900 | Also yes | 07:17:12 |
K900 | The AMD driver can inject FSR2 into basically anything | 07:17:22 |
K900 | And they also have "AMD Fluid Motion Frames" which is kinda FSR3 frame gen retrofitted to be purely spatial | 07:17:42 |
K900 | That can be injected into uh | 07:17:54 |
olivia | my impression reading through the vkd3d-proton stuff earlier was that there was a bunch of driver interaction that existed for effectively no reason | 07:17:58 |
K900 | Some things, but not all of them? | 07:17:58 |