07-05-2012, 08:17 AM
07-05-2012, 09:05 AM
Yeah dolphin was only using 2 cores of your cpu and now it uses 3 so you can see why its working better 

07-05-2012, 10:15 PM
and if you add lock threads to cores
its even better 
less heating as well
its even better 
less heating as well
07-06-2012, 06:44 AM
Quote:and if you add lock threads to cores Tongue its even better Smile
less heating as well
Turning lock threads to cores on/off should not change cpu load or heat emission at all.
07-06-2012, 09:21 AM
(07-06-2012, 06:44 AM)NaturalViolence Wrote: [ -> ]Turning lock threads to cores on/off should not change cpu load or heat emission at all.
If anything, temps would go up a bit on certain cores because the operating system wouldn't be able to perform any load balancing.
07-06-2012, 11:22 AM
Lets not discuss something so trivial as that..
![[Image: lockb.jpg]](http://img31.imageshack.us/img31/8623/lockb.jpg)
Dolphin uses massive amount of cpu if not locked in latest git build
its not like in old times r6505 where cpu usage would not even be seen
Super mario galaxy known cpu eater
Do you see Less heating part now?
And just to be clear
there is no speed loss!
Dolphin just doesn't understand how to divide properly and it eats it all
![[Image: lockb.jpg]](http://img31.imageshack.us/img31/8623/lockb.jpg)
Dolphin uses massive amount of cpu if not locked in latest git build
its not like in old times r6505 where cpu usage would not even be seen
Super mario galaxy known cpu eater
Do you see Less heating part now?
And just to be clear
there is no speed loss!
Dolphin just doesn't understand how to divide properly and it eats it all
07-06-2012, 12:19 PM
Thats patent bullshiv
07-08-2012, 07:55 AM
Quote:Dolphin uses massive amount of cpu if not locked in latest git build
its not like in old times r6505 where cpu usage would not even be seen
Super mario galaxy known cpu eater
Do you see Less heating part now?
And just to be clear
there is no speed loss!
Dolphin just doesn't understand how to divide properly and it eats it all
Unless there is some horrible bug with dolphin it's not possible for it to be using twice as much processing power with no improvement in performance just from turning lock threads to cores on/off. I call BS and request proof.
Quote:If anything, temps would go up a bit on certain cores because the operating system wouldn't be able to perform any load balancing.
That doesn't make any sense. If the cpu load remains the same the thermal emissions should remain the same regardless of whether the OS or application is managing the thread affinity.
07-08-2012, 10:07 PM
(07-08-2012, 07:55 AM)NaturalViolence Wrote: [ -> ]That doesn't make any sense. If the cpu load remains the same the thermal emissions should remain the same regardless of whether the OS or application is managing the thread affinity.
But cpu load per core doesnt remain the same,so its posible that locking threads to core could produce more heat,since for example core 1 would get much more load then it would with it off,so it will produce more heat as well.
But then also core 2 would get much less load and would produce less heat.
But question is why do you think that for example core 1 load 50% core 2 load 50% core 3 load 50% core 4 load 50% would produce same amount of heat as core 1 load 90% core 2 load 10% core 3 load 90% core 4 load 10%?
I think more the core is loaded,it will provide substantially more heat.
To explain it even simpler : I think just one core beeing loaded 100% would provide more heat then 2 cores beeing loaded 50% althrough they will do same amount of work
07-09-2012, 08:15 AM
Quote:But cpu load per core doesnt remain the same,so its posible that locking threads to core could produce more heat,since for example core 1 would get much more load then it would with it off,so it will produce more heat as well.
But then also core 2 would get much less load and would produce less heat.
TOTAL load.
Quote:But question is why do you think that for example core 1 load 50% core 2 load 50% core 3 load 50% core 4 load 50% would produce same amount of heat as core 1 load 90% core 2 load 10% core 3 load 90% core 4 load 10%?
Similar, not the same. And because we have data to suggest this.
Every operation a microprocessor performs has a specific power consumption, including NOPs (no operation, or idle cycle). A specific operation will consume a specific amount of power regardless of which core is performing the operation. Per-core heat emission will change but total heat emission will not change. Since the cores are identical it does not matter where the operations are being performed so long as the same operations are being performed.
Any difference in thermal emission will be due to the OS performing task switching and will so small as to be negligible.
Quote:I think more the core is loaded,it will provide substantially more heat.
To explain it even simpler : I think just one core beeing loaded 100% would provide more heat then 2 cores beeing loaded 50% althrough they will do same amount of work
The math that AMD is using for turboCore is based on that statement being wrong.