There are currently three parameters for tuning the GPU load - GPU-Accel (workload tuning), GPU-Loops, and (for plus) segment size.
While I'm sure all of these are quite meaningful for those familiar with the intricacies of GPU architecture, they are much less so for regular folks.
I recently updated from a GTX560 to a HD6990.
For a given test case using the same tuning parameters, both GPU's go to 99% load. (Don't know if they're working efficiently, but they're busy...)
The GTX560 runs at a quite 82C, whereas the HD6990 sounds like a jet engine at 92C.
Here's what I would like to see.
Suggestion #1 - Allow the user to simply input GPU load, as a percentage. The application would chose efficient values for the tuning parameters, based on the attack type, etc., adjusting at runtime to meet the selected load.
Also, my experience above showed the rather abrupt exit (exception thrown?) when exceeding the watchdog temp, which also didn't seem to fully clean up (there was a file with a ".new" extension.)
Suggestion #2 - Instead of a rather inelegant abort, the application should "dial back" it's load to keep it within the selected temperature.
Alternative to the above - add tuning parameters "best practices" to the wiki.
Thanks for all the great work.
While I'm sure all of these are quite meaningful for those familiar with the intricacies of GPU architecture, they are much less so for regular folks.
I recently updated from a GTX560 to a HD6990.
For a given test case using the same tuning parameters, both GPU's go to 99% load. (Don't know if they're working efficiently, but they're busy...)
The GTX560 runs at a quite 82C, whereas the HD6990 sounds like a jet engine at 92C.
Here's what I would like to see.
Suggestion #1 - Allow the user to simply input GPU load, as a percentage. The application would chose efficient values for the tuning parameters, based on the attack type, etc., adjusting at runtime to meet the selected load.
Also, my experience above showed the rather abrupt exit (exception thrown?) when exceeding the watchdog temp, which also didn't seem to fully clean up (there was a file with a ".new" extension.)
Suggestion #2 - Instead of a rather inelegant abort, the application should "dial back" it's load to keep it within the selected temperature.
Alternative to the above - add tuning parameters "best practices" to the wiki.
Thanks for all the great work.