Huh? You’re talking about the Blender numbers? These are not facts but just some random numbers done with some software on different hardware in passive benchmarking mode. Passive benchmarking does not allow to generate any insights, collecting those numbers without meaning is not useful other than providing numbers clueless people can base decisions on (benchmarking as marketing instrument).
What we need is ACTIVE BENCHMARKING to generate insights.
It’s totally irrelevant how software A performs on 3 different SBC when it’s about getting an idea why software B starts to behave weird after some time on the Vim2. And I only wanted to give a hint to @NicoD that your remarks about armhf vs. arm64 or even ‘A32 emulation mode on A64 (via hypervisor)’ are misleading since there is no such thing.
He uses kdenlive Ubuntu Xenial arm64 distro packages on both ODROID-C2 and Vim2 and those require of course on both boards also running a 64-bit kernel since otherwise you can’t execute arm64 packages. There is also no hypervisor involved and of course also no ‘emulation’ whatsoever (if he would be running armhf software that would be a matter of Debian Multiarch which allows to simply add armhf packages to arm64 installs… but we’re not talking about this here).
The only question is why kdenlive starts to stop utilizing all CPU cores after some time. And this needs to be diagnosed if we want some insights. At least it’s not related to 32-bit vs. 64-bit.
No, I was only talking about
armbianmonitor's ability to report different clockspeeds when there’s more than one CPU cluster. This does not require anything inside the kernel only the existence of a
cpu4 node. Then
armbianmonitor will show cpufreq values for both clusters but this is of no great use with S912 since the clockspeed values are faked anyway.
If you were talking about getting the scheduler to behave more properly (sending demanding tasks to the faster little cores instead of those limited to 1 GHz) then it might make some sense but I wonder why these settings are not already in place. Even if it’s not big.LITTLE at all here the weird big.LITTLE emulation mode artificially bottlenecking 4 cores to 1 GHz requires prefering CPU cores 0-3 for demanding tasks…