+- 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: PR #3351 introduced a performance regression (/Thread-pr-3351-introduced-a-performance-regression)
Pages:
1
2
RE: [SOLVED] PR #3351 introduced a performance regression - kirbypuff - 01-10-2016
(12-22-2015, 08:57 AM)kirbypuff Wrote: Fixed (!) in 4.0-8396...
... but the performance regression is back (with a vengeance) starting with 4.0-8634 [= the ffmpeg merge].
4.0-8631 is the last good version without the slowdown issue.
RE: PR #3351 introduced a performance regression - kirbypuff - 01-12-2016
And it got fixed again in 4.0-8672? Interesting...
Definitely a weird issue with the automated build system.
It would be even more interesting to see if a "plain vanilla" VS2015u1 Win-x64 test build by someone else (not by the Dolphin auto-builder) fixes the huge performance regression mentioned in the other thread.
Ishiiruka doesn't have that issue, so it must be a certain compiler flag / switch / script / optimization that was changed/modified or even a stupid typo error.
RE: PR #3351 introduced a performance regression - mbc07 - 01-12-2016
If it's really a performance regression why nobody else can reproduce it?
Looks like you're either paranoid or the one needing a bug fix, not Dolphin
RE: PR #3351 introduced a performance regression - kirbypuff - 01-12-2016
Update: Tested five different PR Test builds, all based on 4.0-8668 with trivial / mobile-only PRs that shouldn't affect the performance of the desktop version.
3 of them had the slowdown issue, 2 of them didn't.
RE: PR #3351 introduced a performance regression - leolam - 01-15-2016
But there wasn't any compiler change or flag change recently, as far as I know from looking in the commits… How about trying it with a real benchmark like the povray? Running the builds several times, perhaps on several computers, building yourself to confirm that there's a regression? As it stands, it's hard to believe that completely unrelated changes affect performance.