• Login
  • Register
  • Dolphin Forums
  • Home
  • FAQ
  • Download
  • Wiki
  • Code


Dolphin, the GameCube and Wii emulator - Forums › Dolphin Emulator Discussion and Support › Development Discussion v
« Previous 1 ... 16 17 18 19 20 ... 116 Next »

Massive difference in performance between commits
View New Posts | View Today's Posts

Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
Thread Modes
Massive difference in performance between commits
08-29-2018, 01:46 AM
#1
vladtheimpaler Offline
Junior Member
**
Posts: 8
Threads: 4
Joined: Jul 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.
Find
Reply
08-29-2018, 06:23 AM (This post was last modified: 08-29-2018, 06:25 AM by JMC47.)
#2
JMC47 Offline
Content Producer
*******
Content Creators (Moderators)
Posts: 6,542
Threads: 29
Joined: Feb 2013
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 Big Grin
Find
Reply
08-29-2018, 06:49 AM
#3
JonnyH Offline
Shameless AMD shill
**********
Developers (Some Administrators and Super Moderators)
Posts: 701
Threads: 0
Joined: May 2017
(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 Big Grin


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.)
Find
Reply
« Next Oldest | Next Newest »


  • View a Printable Version
  • Subscribe to this thread
Forum Jump:


Users browsing this thread: 1 Guest(s)



Powered By MyBB | Theme by Fragma

Linear Mode
Threaded Mode