Originally Posted by
kjeldoran
I started to use this app_info this evening. Yes, you lose your work for your CPU, but if you are focusing only on HCC then you will complete more WUs than using both your CPU and GPU based on my observations with my setup.
Previously, I was doing GPU WUs around 1:56 with only one WU and 7 CPU threads. Using the above app_info, I lose all of my CPU threads but I work on 2 GPU WUs at once. Completion times around around 2:06 to 2:20 per WU. Yes, it is slower but I am completing two WUs at once. Even if I had the max of 2:20 per WU that is over 1200 WUs in one day. Of course, there will be variations and even if it was only 1100 WUs it is still more than what I would get with 7 CPU threads and 1 GPU thread running HCC (which is around 900 WUs in one day at 1:56 per GPU WU). I'd really only recommend the above app_info if you run HCC only and your GPU is able to handle the work.
You can also do more than 2 GPU WUs at once if you change <count>0.500000</count> to .33 (3 at once) or .25 (4 at once). Info was taken from nanoprobe on WCG forums for increasing the number of WUs beyond 2.
Pros:
Decreased power consumption since only 2 threads are being used on the CPU
More WUs completed
Cons:
Only able to run HCC GPU at this point in time, maybe there can be code added to run another project later on.
More stress on the video card
Some video cards may not benefit from this app_info
I am still in the testing phase of this and I will see how the results are in the next few days. I might see if changing the count to 3 or 4 can increase overall WU completion.
Last thing, I would imagine using this tweak will show a greater effect when the core clock is increased since the GPU is being utilized more.