03-06-2016, 03:06 PM
Benchmark comparisons like this are not useful. You need to include thermal information (eg. heat sink, fan) temperature and thermal throttling details as well including environment temperature. Also you need to make sure that you did loose any cores during one benchmark and then run the next with only 2 or even 1 core (once they are off, they are not turned on again).
This is easy to do with RPi monitor which can easily be installed on the Pine64 with the script from @tkaiser: http://kaiser-edv.de/tmp/4U4tkD/install-...for-a64.sh
Share the graphs which capture the test runs.
Also i have some scripts to monitor on the command line at https://github.com/longsleep/build-pine6...rm-scripts and to turn disabled cores back on.
This are the thermal results running my optimized BSP on the Pine64 without heat sink at 23C room temperature while the pine lies flat on the table without enclosure.
idle
1 cpuburn-a8
2 cpuburn-a8
3 cpuburn-a8
4 cpuburn-a8
This means, it runs stable at 816.00 MHz in cooling state 3 at around 90C with 4 cores burning with a8 optimized code. To add more load, run the cpuburn-53 code which utilized the full CPU capabilities and draws a lot more power / heat.
Also there is the undervoltage problem. If your Pine crashes/freezes it is not because of the heat - most likely you draw too much power and the USB cable / Power supply cannot provide it. Use better/shorter USB cable and another better power supply in such cases.
Cpuburn tools for arm: https://github.com/ssvb/cpuburn-arm
NOTE: Be careful with tuning the thermal details and running cpuburn - you can damage things!
This is easy to do with RPi monitor which can easily be installed on the Pine64 with the script from @tkaiser: http://kaiser-edv.de/tmp/4U4tkD/install-...for-a64.sh
Share the graphs which capture the test runs.
Also i have some scripts to monitor on the command line at https://github.com/longsleep/build-pine6...rm-scripts and to turn disabled cores back on.
This are the thermal results running my optimized BSP on the Pine64 without heat sink at 23C room temperature while the pine lies flat on the table without enclosure.
idle
Code:
# pine64_health.sh
CPU freq : 480.00 MHz
CPU count : 4
Governor : interactive
Core voltage : 1.04 V
SOC Temp : 38 C
Cooling state : 0
Cooling limit : roomage:0,0,0,0,1152000,4,0,0
1 cpuburn-a8
Code:
# pine64_health.sh
CPU freq : 1152.00 MHz
CPU count : 4
Governor : interactive
Core voltage : 1.30 V
SOC Temp : 56 C
Cooling state : 0
Cooling limit : roomage:0,0,0,0,1152000,4,0,0
2 cpuburn-a8
Code:
pine64_health.sh
CPU freq : 1104.00 MHz
CPU count : 4
Governor : interactive
Core voltage : 1.26 V
SOC Temp : 74 C
Cooling state : 1
Cooling limit : roomage:0,0,0,0,1152000,4,0,0
3 cpuburn-a8
Code:
pine64_health.sh
CPU freq : 1008.00 MHz
CPU count : 4
Governor : interactive
Core voltage : 1.20 V
SOC Temp : 84 C
Cooling state : 2
Cooling limit : roomage:0,0,0,0,1152000,4,0,0
4 cpuburn-a8
Code:
# pine64_health.sh
CPU freq : 816.00 MHz
CPU count : 4
Governor : interactive
Core voltage : 1.20 V
SOC Temp : 91 C
Cooling state : 3
Cooling limit : roomage:0,0,0,0,1152000,4,0,0
This means, it runs stable at 816.00 MHz in cooling state 3 at around 90C with 4 cores burning with a8 optimized code. To add more load, run the cpuburn-53 code which utilized the full CPU capabilities and draws a lot more power / heat.
Also there is the undervoltage problem. If your Pine crashes/freezes it is not because of the heat - most likely you draw too much power and the USB cable / Power supply cannot provide it. Use better/shorter USB cable and another better power supply in such cases.
Cpuburn tools for arm: https://github.com/ssvb/cpuburn-arm
NOTE: Be careful with tuning the thermal details and running cpuburn - you can damage things!