Quote: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.
well, the idea is good. but the reality is so different. for example, manually adjust oclHashcat to run only with 90% gpu utilization. you can start playing fps hungry games in background without loosing frames. i think the gpu utilization meter is to inaccurate.
Quote:Suggestion #2 - Instead of a rather inelegant abort, the application should "dial back" it's load to keep it within the selected temperature.
absolutly not. this would create an huge code overhead. also, every user wants it different. no, just find your acceptable utilzation manually. you will notice there is some point the temps will not exceed, regardless of the time.