![]() |
|
Massive difference in performance between commits - Printable Version +- Dolphin, the GameCube and Wii emulator - Forums (https://forums.dolphin-emu.org) +-- Forum: Dolphin Emulator Discussion and Support (https://forums.dolphin-emu.org/Forum-dolphin-emulator-discussion-and-support) +--- Forum: Development Discussion (https://forums.dolphin-emu.org/Forum-development-discussion) +--- Thread: Massive difference in performance between commits (/Thread-massive-difference-in-performance-between-commits) |
Massive difference in performance between commits - vladtheimpaler - 08-29-2018 Hello, I have noticed something very odd between commits. the more-recent one: 3d560630f5c149b4eff85ad43a73d7f53dab083a 2 commits before: 8206e4862c172e065967ce5d18cac55bbd78279e So I tried F-Zero GX on the newest commit & it stays at around 30 fps.... but the '2 commits before' one gets 60 fps. Seems like a massive difference. I've tried changing configurations to no avail, but once I re-installed the older commit I got 60 FPS again. I hope my noticing this leads to an improvement in performance! F-Zero GX typically would never play well for me unless I over-clocked it to 400% CPU emulation, now I do not have to do that, it "just works" at 60 fps! I am using Vulkan, on a Nvidia GT 1030, nonfree drivers - Arch Linux derivative. 3.5GHz 6-core AMD FX-6300, 16GB DDR3 RAM @ 1600MHz. RE: Massive difference in performance between commits - JMC47 - 08-29-2018 There are literally no differences that could affect performance unless there's some issue with logging. Edit: JMC can't read still. Apparently a Vulkan work-around was removed as well. Your drivers might be broken
RE: Massive difference in performance between commits - JonnyH - 08-29-2018 (08-29-2018, 06:23 AM)JMC47 Wrote: Edit: JMC can't read still. Apparently a Vulkan work-around was removed as well. Your drivers might be broken It was a workaround for AMD drivers only - it shouldn't affect /anything/ on an nvidia system. Looking at the commit I can't see anything wrong - maybe that was a bad bisect? Or you've got some unexpected settings that are getting picked up by some copies? Or there's another system issue at work (some throttling, load from another process etc.) |