Why performance is higher on LITTLE cores?

#!/bin/bash

for cpufreq in `ls -d /sys/devices/system/cpu/cpufreq/policy*`
do
    echo "Working on ${cpufreq}"
    gov=`cat ${cpufreq}/scaling_governor`
    echo "${cpufreq} currently using \"${gov}\" governor, will force to performance"
    sudo bash -c "echo performance > ${cpufreq}/scaling_governor"
    sudo bash -c "echo 0 > ${cpufreq}/stats/reset"
    cat ${cpufreq}/stats/trans_table
    echo ""
done

for devfreq in `ls -d /sys/class/devfreq/*`
do
    echo "Working on ${devfreq}"
    IFS=', ' read -r -a array <<< `cat ${devfreq}/available_governors`
    # echo "${array}"
    if [[ " ${array[@]} " =~ " performance " ]]; then
        echo "== performance governor available for ${devfreq}, will use it"
        sudo bash -c "echo performance > ${devfreq}/governor"
    fi
    sudo bash -c "echo 0 > ${devfreq}/trans_stat"
    cat ${devfreq}/trans_stat
done

echo "remember to reset governors at the end"



# YOUR BENCHMARK

for cpufreq in `ls -d /sys/devices/system/cpu/cpufreq/policy*`
do
    echo "Working on ${cpufreq}"
    cat ${cpufreq}/stats/trans_table
done

for devfreq in `ls -d /sys/class/devfreq/*`
do
    echo "Working on ${devfreq}"
    cat ${devfreq}/trans_stat
done

zois said:

May I ask, is there a benefit in unplugging the cores I am not using? Or that is an alternative approach to using `tasket`?

By offlining all CPU cores of a big or LITTLE cluster, you will remove the cluster from the data cache coherency domain at the hardware level.

See big.LITTLE.Whitepaper.pdf (hexus.net).

With `taskset`, you just force the Linux scheduler to run your code on the CPUs provided.

#!/bin/bash

for cpufreq in `ls -d /sys/devices/system/cpu/cpufreq/policy*`
do
    echo "Working on ${cpufreq}"
    gov=`cat ${cpufreq}/scaling_governor`
    echo "${cpufreq} currently using \"${gov}\" governor, will force to performance"
    sudo bash -c "echo performance > ${cpufreq}/scaling_governor"
    sudo bash -c "echo 0 > ${cpufreq}/stats/reset"
    cat ${cpufreq}/stats/trans_table
    echo ""
done

for devfreq in `ls -d /sys/class/devfreq/*`
do
    echo "Working on ${devfreq}"
    IFS=', ' read -r -a array <<< `cat ${devfreq}/available_governors`
    # echo "${array}"
    if [[ " ${array[@]} " =~ " performance " ]]; then
        echo "== performance governor available for ${devfreq}, will use it"
        sudo bash -c "echo performance > ${devfreq}/governor"
    fi
    sudo bash -c "echo 0 > ${devfreq}/trans_stat"
    cat ${devfreq}/trans_stat
done

echo "remember to reset governors at the end"



# YOUR BENCHMARK

for cpufreq in `ls -d /sys/devices/system/cpu/cpufreq/policy*`
do
    echo "Working on ${cpufreq}"
    cat ${cpufreq}/stats/trans_table
done

for devfreq in `ls -d /sys/class/devfreq/*`
do
    echo "Working on ${devfreq}"
    cat ${devfreq}/trans_stat
done

zois said:

May I ask, is there a benefit in unplugging the cores I am not using? Or that is an alternative approach to using `tasket`?

By offlining all CPU cores of a big or LITTLE cluster, you will remove the cluster from the data cache coherency domain at the hardware level.

See big.LITTLE.Whitepaper.pdf (hexus.net).

With `taskset`, you just force the Linux scheduler to run your code on the CPUs provided.

For instance, on another board which implements a different big.LITTLE configuration (Hardkernel Odroid-XU3/4 with A7x4-A15x4), I have seen some nasty weird results with "bad" cluster frequencies configuration. The issue was about data cache coherency mechanism which was playing hard depending on CPU frequencies (see https://dl.acm.org/doi/10.1145/3372799.3394370). However, on the HiKey970 it's unlikely that the bad perf on the big is related to the same issue found in this study as the data cache coherency mechanism is a bit different with the use of a snoop filter.

One thing to maybe have DDR frequency working and all other files that I mention is to bump your kernel version? But I don't know if a newer kernel version has this supported ...

I suggest you check with performance counters to have a more in-depth clue about what the hardware is actually doing beyond the OS.

Also, you could have a try running both clusters at the same (high) frequency if it's possible? So you could see if the hardware doesn't favour your code with deep hardware feature available on one or the other CPU type.

After a bit of research: this paper https://arxiv.org/pdf/1908.11450.pdf seems to be related to what you're looking for. Their results on ResNet50 seems to contradict your results. Maybe triple check your scripts?

Meanwhile, I will try to have my hand on this board.

[...]

Finally, I had my hand on a board. It seems that the board heats up quite easily.

Please, try to monitor thermal states while running your code in parallel:

#!/bin/bash

while true;
do
    echo "===";
    echo "temperature";
    cat /sys/devices/virtual/thermal/thermal_zone*/temp;
    echo "cooling state";
    cat /sys/devices/virtual/thermal/cooling_device*/cur_state;
    sleep 0.1;
done

You may need to investigate deeper, probably with performance counters.
You could use Streamline to do so: developer.arm.com/.../streamline-performance-analyzer

Having a fixed DDR frequency would be nice. Instead of the unavailable performance governor, you could force a min and max range:

cat /sys/class/devfreq/ddr_devfreq/available_frequencies
415000000 830000000 1244000000 1866000000

sudo bash -c "echo 1866000000 > /sys/class/devfreq/ddr_devfreq/min_freq"
sudo bash -c "echo 1866000000 > /sys/class/devfreq/ddr_devfreq/max_freq"

Also, try to use the same frequency on both cluster.

cat /sys/devices/system/cpu/cpufreq/policy0/scaling_available_frequencies
509000 1018000 1210000 1402000 1556000 1690000 1844000
cat /sys/devices/system/cpu/cpufreq/policy4/scaling_available_frequencies
682000 1018000 1210000 1364000 1498000 1652000 1863000 2093000 2362000

sudo bash -c "echo performance > /sys/devices/system/cpu/cpufreq/policy0/scaling_governor"
sudo bash -c "echo 1018000 > /sys/devices/system/cpu/cpufreq/policy0/scaling_max_freq"

sudo bash -c "echo performance > /sys/devices/system/cpu/cpufreq/policy4/scaling_governor"
sudo bash -c "echo 1018000 > /sys/devices/system/cpu/cpufreq/policy4/scaling_max_freq"

Remember to continue monitoring temperature, and frequency change while you're investigating.
You could also limit distraction for your hardware by removing "useless" processes, like removing all "unneeded" background services and running all in serial console, without any GUI running. It will limit a bit context switching and some other annoyance for your application.