We tweaked the settings a bit yesterday (defining a few more dvfs operating points -- see below -- and cpufreq steps and also increased the thermal trip points a bit. The 1st was set to 65°C before and is now at 80°C which helps a lot with single threaded workloads).
New results here: http://openbenchmarking.org/result/16031...603109GA38 (these can not be compared with the previous results except of the "Pine64+ ARMv8 -O3" entry that shared the same compiler switches).
I'm still not satisfied with these settings since as soon as single threaded workloads lead to the SoC temperature exceeding 80°C slight throttling occurs but since I already try to simulate worst case conditions (Pine64+ inside a small cardboard box only wearing a cheap heatsink) and this only sometimes happens the settings are ok more or less:
![[Image: Pine64_in_Enclosure_with_Heatsink_higher...points.png]](http://kaiser-edv.de/tmp/mc6CyL/Pine64_in_Enclosure_with_Heatsink_higher_trip_points.png)
Two more tests will follow with identical settings that will only differ with multithreaded workloads since there throttling will jump in. I removed the cardboard box and will test with the Pine64+ lying flat on the table at 23°C ambient temperature. One test only with heatsink and the other with another Pine64+ without heatsink but small fan trying to blow some air over the SoC's surface (to answer the most important question regarding benchmarks for every more recent SoC: does using a heatsink or a fan is more efficient?)
![[Image: Pine64_Plus_Heatsink_vs_Fan.jpg]](http://kaiser-edv.de/tmp/mc6CyL/Pine64_Plus_Heatsink_vs_Fan.jpg)
[1] Dynamic voltage frequency scaling settings used now:
New results here: http://openbenchmarking.org/result/16031...603109GA38 (these can not be compared with the previous results except of the "Pine64+ ARMv8 -O3" entry that shared the same compiler switches).
I'm still not satisfied with these settings since as soon as single threaded workloads lead to the SoC temperature exceeding 80°C slight throttling occurs but since I already try to simulate worst case conditions (Pine64+ inside a small cardboard box only wearing a cheap heatsink) and this only sometimes happens the settings are ok more or less:
![[Image: Pine64_in_Enclosure_with_Heatsink_higher...points.png]](http://kaiser-edv.de/tmp/mc6CyL/Pine64_in_Enclosure_with_Heatsink_higher_trip_points.png)
Two more tests will follow with identical settings that will only differ with multithreaded workloads since there throttling will jump in. I removed the cardboard box and will test with the Pine64+ lying flat on the table at 23°C ambient temperature. One test only with heatsink and the other with another Pine64+ without heatsink but small fan trying to blow some air over the SoC's surface (to answer the most important question regarding benchmarks for every more recent SoC: does using a heatsink or a fan is more efficient?)
![[Image: Pine64_Plus_Heatsink_vs_Fan.jpg]](http://kaiser-edv.de/tmp/mc6CyL/Pine64_Plus_Heatsink_vs_Fan.jpg)
[1] Dynamic voltage frequency scaling settings used now:
Code:
max_freq = <1152000000>;
min_freq = <480000000>;
lv_count = <8>;
lv1_freq = <1152000000>;
lv1_volt = <1300>;
lv2_freq = <1104000000>;
lv2_volt = <1260>;
lv3_freq = <1056000000>;
lv3_volt = <1240>;
lv4_freq = <1008000000>;
lv4_volt = <1200>;
lv5_freq = <960000000>;
lv5_volt = <1160>;
lv6_freq = <912000000>;
lv6_volt = <1120>;
lv7_freq = <816000000>;
lv7_volt = <1080>;
lv8_freq = <648000000>;
lv8_volt = <1040>;