cpu temp doing compiles

[stevea]

Originally Posted by juszczec

Can you describe the test you are doing where you hit a peak of 71C? I'd like to do the same thing on my system and see what happens.

I ONLY ever see temps above 80C if I compile MAME or if I run a graphically intensive game. Under average use (including other software compiles), I typically see temps between 50-55C.

Mark

Just do this once for each core (two times in your case, four for me)
dd if=/dev/zero of=/dev/null &
Then wait several minutes for it to heat up.

You can see these jobs with
jobs
You can selectively kill the jobs (see 'jobs' command output) with
kill %1
or
kill %2


This won't exercise the disk which could add to the temperature.
I suppose you could
sudo dd if=/dev/sda of=/dev/null &

[juszczec]

Hi folks

So here are the results of some testing I did.

This test put the system under a bit of load and exercised the hard drive. The numbers to the right of the time are the temps of the 4 cores in C:

Gnome Terminal, gedit, Google Chrome (2 tabs, gmail and fedoraforum.org) running
ran "sudo dd if=/dev/sda of=/dev/null" 2x

8:12am 53, 48, 51, 51
8:13am 55, 49, 53, 52
8:14am 55, 50, 53, 52
8:15am 55, 50, 54, 53
8:16am 56, 51, 54, 54
8:17am 56, 51, 55, 55

No big deal.

Here are the results of exercising the cpu's only:

Gnome Terminal, gedit, Google Chrome (2 tabs, gmail and fedoraforum.org) running
ran dd if=/dev/zero of=/dev/null & 2x

8:34 53, 48, 51 51
8:35 70, 69, 70, 74
8:36 85, 84, 83, 89

Once we got to almost 90C I interrupted the test.

So what does this tell me? I'm not even sure if this is abnormal or cause for concern.

Mark

[juszczec]

So here's how I solved my problem.

I created a wrapper script for gcc. It uses 'sensors' to get the temp of all 4 cores. If any of them are above an arbitrary number (70, in this case) it will pause until all 4 temps drop below this arbitrary number.

My problem came up when compiling Advance MAME for my FC14 system.

I grabbed the floating point code from a Linux Journal article I found online.

Here's my code. In order to use it, save it in a file called gcc, place its location in your PATH before wherever the real gcc is installed and watch your cpu stay relatively cool:

#!/bin/bash

float_scale=2

function float_cond()
{
local cond=0
if [[ $# -gt 0 ]]; then
cond=$(echo "$*" | bc -q 2>/dev/null)
if [[ -z "$cond" ]]; then cond=0; fi
if [[ "$cond" != 0 && "$cond" != 1 ]]; then cond=0; fi
fi
local stat=$((cond == 0))
return $stat
}

set -f
cutoff=70.00
waitToCool=1

while [ $waitToCool -eq 1 ]
do
core1=`sensors -u | grep ^" temp1" | awk '{print $2}'`
core2=`sensors -u | grep ^" temp2" | awk '{print $2}'`
core3=`sensors -u | grep ^" temp3" | awk '{print $2}'`
core4=`sensors -u | grep ^" temp4" | awk '{print $2}'`

if float_cond "$core1 < $cutoff"; then
waitToCool=0
else
waitToCool=1
fi
if float_cond "$core2 < $cutoff"; then
waitToCool=0
else
waitToCool=1
fi
if float_cond "$core3 < $cutoff"; then
waitToCool=0
else
waitToCool=1
fi
if float_cond "$core4 < $cutoff"; then
waitToCool=0
else
waitToCool=1
fi

if [ $waitToCool -eq 1 ]; then
sleep 5
fi
done
set +f
exec /usr/bin/gcc "$@"