01-08-2012, 11:14 PM
I been wondering this for a long time.. since I think it was around r3137 or so, the old GUI PCSX2 where setting X software rendering threads actually used that many threads or appeared to.
Now I am using the latest SVN from the build bot with all settings default, MTVU is off as its reducing FPS and appearing to make the "threading issue" worse, speed hacks all off. With my desktop system in my profile I put render threads to 7, I get output like this:
If I set 8 (yes I know PCSX2 needs its own thread) it slows down slightly but still doesnt use even close to whats set, I would think all threads would be near 100%? The older versions of PCSX2/GSdx didnt behave like so for software mode and was giving more FPS in that same spot in the game, doesn't look like EE is the cause or GS going by the window's display load. In the most intense spots like this, 3 threads are dead and the ones in use are barely over half and this is with 7 render threads set. Is there a reason for this? It a bug? Would like to know.
Now I am using the latest SVN from the build bot with all settings default, MTVU is off as its reducing FPS and appearing to make the "threading issue" worse, speed hacks all off. With my desktop system in my profile I put render threads to 7, I get output like this:
If I set 8 (yes I know PCSX2 needs its own thread) it slows down slightly but still doesnt use even close to whats set, I would think all threads would be near 100%? The older versions of PCSX2/GSdx didnt behave like so for software mode and was giving more FPS in that same spot in the game, doesn't look like EE is the cause or GS going by the window's display load. In the most intense spots like this, 3 threads are dead and the ones in use are barely over half and this is with 7 render threads set. Is there a reason for this? It a bug? Would like to know.