Dolphin, the GameCube and Wii emulator - Forums

I'm not complaining at all. But I was asked to make a new thread about this.

From what I've been told, Dolphin produces 2 threads of processing. Enabling "Lock threads to cores" option, is supposed to restrict each thread to just one core. Leave it off, and the threads jump around however many cores you have, and this is supposed to be less efficient, according to the "experts".

This is with "Lock threads to cores" off:


This is with it on:


It seems to still be using other cores. Maybe that's a good thing. But others have said it only uses 2 cores on their CPU, even if it's maxing them out.

If you wish to participate, try enabling this feature, and tell whether Dolphin's threads use more than 2 cores, or not. And include what kind of processor you are using, and other relevant specs. Thanks.

This test is only for quad core CPUs. If you have a dual core, don't bother with it.

Never happened to me

Dolphin uses more than 2 threads, so it'll use more than 2 cores. Dolphin can use up to 7 or 8 threads in some situations (e.g. in a Wii game using 4 real wiimotes while creating a save state).

@Skid

I was trying to get a hold of you on irc the last couple of days to ask you about why this might be happening. And for some reason you didn't notice the original thread.

Anyways from what I understand, the threads include:
-CPU (runtime interpreter/jit recompiler/jitil recompiler)
-GPU (runtime compiler)
-DSP
-GUI
-Audio backend
-Input
-Input #2 (if present)
-Input #3 (if present)
-Input #4 (if present)

But from what I understand the last 6 should use almost no processing power, 1-2% at most. And the DSP thread isn't seperated unless the DSPLLE on thread option is used. Am I wrong in either of those two assumptions? Or is their something else that I have overlooked that could be accounting for this?

Yeh, I haven't really measured the amount of CPU each thread consumes. I do not think they consume a lot, but added together they might add up to something?

dsp on thread seems to use up nearly 60% of a third core D:

10-20% load of a 3GHz core 2 quad from input/GUI/audio backend!?!? I find that hard to believe even when I have the proof is staring me in the face. I keep thinking their must be some other explanation.

Quote:dsp on thread seems to use up nearly 60% of a third core D:

I'm assuming hypnotoad is not using it though.

NaturalViolence Wrote:I'm assuming hypnotoad is not using it though.

Correct. I'm not using DSP on thread. It says it's not recommended.

btw, Dolphin has up to 20 threads.