Message boards :
Questions and problems :
CPU Temperature vs Performance
Posted 19 Jul 2019 by Tom
I have an idea for future BOINC application development.
It's a problem I have some years.... it gets hot. No, stop giggling, I appreciate its summer causing that.
Being northern European I’m not built for it; I prefer cool and rugged landscapes of snow and ice that make your heart ache with the vistas of rugged beauty…. Sorry, dreaming of Iceland, my most favorite place on the planet. Back on topic…..
While my PC isn’t interested in landscapes, it likes cool too.
Over the years I’ve tried many different combinations of cooling configurations, with my current overclocked PC running with a pressurised liquid-cooling system that works pretty well.
I still can’t run BOINC at maximum in the summer, however. The environment that my PC sits in (my office/man cave) gets really hot in summer owing to poor ventilation, which I can’t do much about. Even with a pretty efficient cooler, the system has nowhere to dump the heat, so core temps get too high over the course of the day. My PC is on pretty much 24/7/365 and grinding on BOINC when I’m not using it.
I know I need to keep an eye on my CPU temperatures in summer, so I wind down the CPU% to keep the peak temperatures around the 80degC mark. In the winter I can push the usage limits to 100% without issue, but in summer I need to wind it back to around 30% of the CPUs 100% of the CPU time.
It occurred to me that I could run BOINC harder more often if there was some link in the software between the application and the CPU temps. If I could set the maximum temperature that I was comfortable with, and the BOINC application was able to read the actual core temps during run time, then BOINC could decide the maximum CPU load usage automatically to maximise output without cooking the host. End result would be the PC running harder, longer, giving much better aggregate productivity.
Just a thought.
Copyright © 2020 University of California. Permission is granted to copy, distribute and/or modify this document under the terms of the GNU Free Documentation License, Version 1.2 or any later version published by the Free Software Foundation.