Isn't it possible to make Dolphin detect a TurboBoost enabled CPU and hide/show LTTC accordingly? Maybe renaming the option (e.g. "Use CPU's TurboBoost") altogether. I do see the main objection with this approach though: if people read "TurboBoost" they might assume a miraculous performance increase.
If not, it should be left as a dev option imho:
NaturalViolence Wrote:...I find it to be a useful option for checking how much load each thread is using and making sure that dolphin is following the correct behavior...
Provide data proving that LTTC has more effect on TurboBoost than setting the process affinity.
According to Parlane LTTC is even slower than certain affinity settings.
(01-18-2013, 06:58 PM)arthur117 Wrote: [ -> ]Isn't it possible to make Dolphin detect a TurboBoost enabled CPU and hide/show LTTC accordingly? Maybe renaming the option (e.g. "Use CPU's TurboBoost") altogether. I do see the main objection with this approach though: if people read "TurboBoost" they might assume a miraculous performance increase.
If not, it should be left as a dev option imho:
The option was never meant to be a "TurboBoost enabler" and "locking threads to cores" is a silly way to enable one.
Quote:The option was never meant to be a "TurboBoost enabler" and "locking threads to cores" is a silly way to enable one.
What's the better way? I mean, that's all the LTTC people want, isn't it? So if there was a way to do it better wouldn't that solve the issue for everyone?
Major Wrote:I mean, that's all the LTTC people want, isn't it?
NaturalViolence Wrote:I find it to be a useful option for checking how much load each thread is using and making sure that dolphin is following the correct behavior
I wish it were replaced by some other method of checking the load on each thread. Billiard thinks we should all use profilers for that but I think that's a bit nuts considering this is so much easier.
This is not an accurate way to measure load. What about spinlocks?
(01-19-2013, 12:01 AM)MaJoR Wrote: [ -> ]Quote:The option was never meant to be a "TurboBoost enabler" and "locking threads to cores" is a silly way to enable one.
What's the better way? I mean, that's all the LTTC people want, isn't it? So if there was a way to do it better wouldn't that solve the issue for everyone?
I believe the "better way" is setting process affinity.
That is the whole purpose of this thread.
People are supposed to tell me if process affinity >= LTTC.
delroth Wrote:This is not an accurate way to measure load. What about spinlocks?
Sure, that's much better. But who's going to do it? I get the feeling that nobody cares about this except me and I'm sure as hell not going to get off my ass to implement a better solution. I'll probably just stick to using older builds in the meantime any time I need to take measurements.
Billiard26 Wrote:I believe the "better way" is setting process affinity.
That is the whole purpose of this thread.
People are supposed to tell me if process affinity >= LTTC.
It's not. But it's way more convenient than having to manually configure the affinity in task manager every time.
You could also use a batch file to start dolphin and set the affinity. Though I think that's only possible in Windows Vista and newer. For Windows XP one could use psexec from microsoft sysinternals. I don't know about Linux and OSX.