Skip to contentSkip to conversation

CPU eaten by unknown code

DISCUSSION [email protected] 1 participant 1 message Dec 24, 2009 1 message not in the archive

lore
Share & tools
lore

A message that is not in the archive (sent off-list or not yet received): [email protected]

#1 lore raw
Quoted 6 lines · Carl

The loop takes 1.2 seconds for about 138 seconds. The loop takes 2.4 second for about 45 seconds. And this repeats forever.

In other words, every 138 seconds something is "running" for 45 seconds and it takes 50% of my CPU time!

Thermal throttling? Is the fan functional? Can you monitor the CPU temperature while running your testcase?

My second guess is something is causing a cpuspeed module to misfire and drop the CPU to a 50% clock speed even though there's load on the system. That one is easily testable - just do a 'grep MHz /proc/cpuinfo' during the 'fast' and 'slow' phases.