-
Notifications
You must be signed in to change notification settings - Fork 169
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
PWR vs TEMP Prioritisation #1716
Comments
I just noticed the prioritisation seems to revert to PWR when switching algos. |
Hi, has there been any progress on this? I'm temporarily running on reduced power limits, but would be great if I could raise them again and allow the temp limits to manage overheating cards. |
Not yet. I'll look into it asap. |
Hi, I've just been thinking about the heating control function in RBM. Please can you tell me if this can be used to penalise hot algos to prevent them from being selected? I list my rigs on MRR and it tends to be that my rigs get hot when someone rents a hot algo. |
Yea it seems to be working. Does it apply an additional price to MRR listings? |
How could I have been so blind! Very good finding! I'll add some switch. |
Thank you |
- add parameter "PriorizeThermalLimit" to ocprofiles.config.txt. Set this to "1" to priorize thermal limit over power limit (issue #1716). Hint: this only works on Windows and Nvidia GPUs.
Added:
|
Hi, I've been having problems with hot cards in this heat and I was investigating why the thermal throttling doesn't work as intended. I noticed that Afterburner has the option to prioritise either PWR or TEMP and by default it's set to PWR which means that cards are allowed to run hotter than the limit if power allows it. Switching this over manually to prioritise temp on the affected cards solved my problem, but I was hoping there might be a way to set it system wide using RBM in some way please?
The text was updated successfully, but these errors were encountered: