Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
EE/VU/IOP Profiling
#1
I know the EE, VU, and IOP emulation is all done on one thread, so that makes usage profiling on the process level nigh impossible. However, due to the microprogram nature of the recompilers, it should be possible to log the amount of microprograms, as well as the type, run by the emulator, right?

Let's use the hypothetical game "Granola Bar Tycoon" as an example. Most of the time, the game runs flawlessly and without any slowdowns. However, during the Raisin Sorting Sudden Death game mode, things are not exactly smooth. But all is not lost. By using the profiler, I could see that EE is not doing much of anything at all, while the VU is on a cocaine induced working spree. By doing this, I realize that during the most intensive parts of the game, the gameplay would benefit from VU cycle stealing and/or EE cycle rate reduction. Likewise, if the IOP has too much on its plate, I could turn down the audio quality.

Anyway, this is just an idea, I don't know if it could work or not, but I would assume having access to such profiling tools would assist in determining which settings and speedhacks to use, which would be much better than the trial and error situation we have right now.

Thanks.

*Watches and waits for Forum Gods to move this into development forum.*
Reply

Sponsored links

#2
Trial and error works fine, there's even a sorta "easy" presets slider to try speed related settings now.

Even when we know a game is mostly VU heavy, all speedhacks like VU cycle stealing could end up doing for that game is break it or just make it go out of sync or just give fake FPS and that's not helping either, would end up going to trial and error again.
Core i5 3570k -- Geforce GTX 670  --  Windows 7 x64
Reply
#3
somewhere in pcsx2's code there's some profiling functions for ee/vu/plugin usage which drk||raziel initially coded.
i fixed them to work again a while back but they probably require fixing again to compile/work.
Check out my blog: Trashcan of Code
Reply
#4
We'll get the internal profiling functionality working (and improved!) again some time.
Reply




Users browsing this thread: 1 Guest(s)