We have a new toy: Athlon 64 X2 4400+ (Socket 939, 2.2GHz, 2*1MB L2
cache), Tyan S2865AG2NRF Tomcat K8E, on-board graphics (ATI Rage XL)
in text mode, 4GB PC3200 DDR SDRAM, 2 300GB hard disks spinning, 1
DVD-RW drive, Tagan TG480-U22 power supply.
Power consumption measured at the mains is (running Linux in text mode):
|------ power ------|
clock idle load 1 load 2
1000MHz 83W 93W 102W
1800MHz 86W 103W 121W
2000MHz 88W 109W 130W
2200MHz 92W 116W 143W
See
http://www.complang.tuwien.ac.at/anton/ ... ption.html
for results on other machines.
We have a new toy: Athlon 64 X2 4400+ (Socket 939, 2.2GHz, 2*1MB L2
cache), Tyan S2865AG2NRF Tomcat K8E, on-board graphics (ATI Rage XL)
in text mode, 4GB PC3200 DDR SDRAM, 2 300GB hard disks spinning, 1
DVD-RW drive, Tagan TG480-U22 power supply.
Power consumption measured at the mains is (running Linux in text mode):
(added voltage according to powernow-k8 driver)
This behaviour is not just bad for the power consumption, but also for
speed for many loads, because the ondemand governor needs some time
until it revs up the chip; OTOH, for longer-running, memory-intensive
loads, this behaviour helps speed.
1000MHz 1100mV 121W 124W 127W 131W 134W
1800MHz 1350mV 161W 171W 181W 191W 202W
2000MHz 1350mV 167W 178W 190W 200W 212W
ondemand 121W 154W 165W/189W
Linux-2.6.14.3 seems to prefer to put the second process on the second
chip, so we usually got the 189W consumption with two non-nice
processes and the ondemand frequency governor; we got the 165W number
This behaviour is not just bad for the power consumption, but also for
speed for many loads, because the ondemand governor needs some time
until it revs up the chip; OTOH, for longer-running, memory-intensive
loads, this behaviour helps speed.
I have seen slides from IDF indicating Intel systems doing voltage
changes in milliseconds *before* they improved the speed. I wonder what
latency people see on shipping systems.
Anton Ertl <anton@mips.complang.tuwien.ac.at> wrote:
This behaviour is not just bad for the power consumption, but also for
speed for many loads, because the ondemand governor needs some time
until it revs up the chip; OTOH, for longer-running, memory-intensive
loads, this behaviour helps speed.
What latency do you see on frequency+voltage changes?
nospam@ab-katrinedal.dk (=?ISO-8859-1?Q?Niels_J=F8rgen_Kruse?=) writes:
Anton Ertl <anton@mips.complang.tuwien.ac.at> wrote:
This behaviour is not just bad for the power consumption, but also for
speed for many loads, because the ondemand governor needs some time
until it revs up the chip; OTOH, for longer-running, memory-intensive
loads, this behaviour helps speed.
What latency do you see on frequency+voltage changes?
With the ondemand governor, I see the speedups happening at
0.70s
0.85s
0.95s
0.80s
0.74s
0.53s
0.95s
0.80s
0.62s
0.94s
0.46s
0.47s
0.62s
0.93s
0.77s
However, I have seen a Windows XP Cool'n'Quiet driver (on a system
with a Winchester Athlon 64) that seemed to react much faster (judging
from the frantic motion of the needle of the speedometer tool provided
with the driver; I did not do measurements), probably faster than
0.1s.
With the ondemand governor, I see the speedups happening at
Anton Ertl wrote:
With the ondemand governor, I see the speedups happening at
Try changing /sys/devices/system/cpu/cpu0/cpufreq/ondemand/sampling_rate
....
I've seen two different minimum rates on two different boards: 670000(us)
and 620000 (Gigabyte, Athlon 3200+, and ASUS Athlon x2 3800+).
Return to Computer Architecture
Users browsing this forum: No registered users and 0 guests