-
Notifications
You must be signed in to change notification settings - Fork 9
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Limit workload based on temperature, fan RPM or GPU/CPU usage #11
Comments
Listening to the microphone has security implications and would over complicate our code. Limiting by temperature, fan RPM or workload would be more practical. |
Having a Current temp on the WU slot would be nice too. it would be a way to notify the user if a PC is showing high temps due to hardware failure and the like. |
Yes, I definitely want this as well. You get SOME control through selecting the number of cores in play, but I'd much rather spread the load through several cores instead of just having one at 100% as well as having finer control of system responsiveness, fan speed, etc. This is especially true for GPU slots. |
I talked to some of my friends and I convinced a few to start running FAH on their (usually fairly powerful) computers at home. They really like the idea and they wanted to help, but they stopped using it in a few days, because they complained about the noise the computer started to make.
It would be great to have one of the following options to set the maximum CPU and GPU payloads in a way that effectively would limit the noise that the computer generates:
(a) the user would define the maximum temperature of CPUs and GPUs in the system
(b) the user would define the maximum RPM of the fans of the system
(c) the user would define the maximum power (in watts) used by each CPU and GPU
(d) the user would define the maximum noise picked up by the microphone [I know this is just a hack, but it might work]
(e) the user would define the maximum workload (as a percentage) for the CPUs and GPUs
The text was updated successfully, but these errors were encountered: