csharpofbflat Wrote:there is no way the cpu is underclocked.
The only way to check for throttling is to use a monitoring application like cpuz running in the background while you're running the application in question. So unless you've done this with another monitoring app (in which case please share) you have no way to guarantee the validity of that statement.
csharpofbflat Wrote:Although I will check the bios power settings again just to make sure.
That will not guarantee that it's not throttling.
csharpofbflat Wrote:the thing that makes little sense to me is that shouldn't dolphin use whatever resources are available to me.
Dolphin uses 2 cores, one to emulate the GC/Wii CPU and another to emulate the GC/Wii GPU. Dolphin also uses your GPU for hardware acceleration. But since you're running at 1x IR you're going to be CPU bottlenecked so the GPU will spend most of its time waiting for new commands from the cpu since it doesn't have much work to do. Dolphin also uses a few hundred megabytes of ram. I'm not sure what you're implying here but I hope I've answered your question.
csharpofbflat Wrote:also setting sensor to 0 was the only way I could get the program to load.
We know, and this is not normal. That's why I said:
NaturalViolence Wrote:Yeah that is weird too. And he shouldn't have to set sensors=0 to get it to boot unless something is seriously wrong with his OS/firmware config.
csharpofbflat Wrote:so the question comes down to am I missing some dolphin settings somewhere that I should change, I think I used all of the TP recomened settings, but I may have missed something.
No the question does not come down to that. Please do what I asked you to do before you jump to conclusions. You're making it very difficult to help you now. Your settings are fine as far as I can tell and so far you have shown no reason to believe otherwise.
csharpofbflat Wrote:also after running burn-in for 48 hours I did not get any errors produced by the CPU or GPU or RAM.
This is irrelevant. All that does is prove that the system is stable. It has nothing to do with dolphin throttling or anything else mentioned here.
csharpofbflat Wrote:I am also leaning more toward a dolphin config issue or hardware issue. Rather than OS because I tried this on 3 different OS's with the same hardware, and viturally the same performance out of each
Which three OS and under what conditions? So far it's looking like a hardware issue to me.
"Normally if given a choice between doing something and nothing, I’d choose to do nothing. But I would do something if it helps someone else do nothing. I’d work all night if it meant nothing got done."
-Ron Swanson
"I shall be a good politician, even if it kills me. Or if it kills anyone else for that matter. "
-Mark Antony
-Ron Swanson
"I shall be a good politician, even if it kills me. Or if it kills anyone else for that matter. "
-Mark Antony
