Hi Thomas, thank you for the insights. Here is the armbianmonitor output. All small letters.
http://ix.io/1byt
Indeed it used more ram than the Khadas, Ill look into why that is. I
ll also try with 4 cores enabled.
I can say that the Odroid C2 also needs a lot of its SWAP. But there is only 1.7GB ram available there. Most of the data moved to swap is not from the videoproject. So I don
t think it slows down the process much.
It is zram that`s being used.
nicod@nanopct3plus:~$ cat /proc/swaps
Filename Type Size Used Priority
/dev/zram0 partition 127816 0 5
/dev/zram1 partition 127816 0 5
/dev/zram2 partition 127816 0 5
/dev/zram3 partition 127816 0 5
/dev/zram4 partition 127816 0 5
/dev/zram5 partition 127816 0 5
/dev/zram6 partition 127816 0 5
/dev/zram7 partition 127816 0 5
<\code>
Its a scientific observation I
ve made
, not a conclusion. I dont know if it
s on all 64-bit octa-cores. I only know that I have seen this behaviour in 64-bit octa-core sbc`s.
Indeed it needs a lot more research to be able to make a conclussion.
It is over the whole project that it appears to have the same problem as the Khadas. I know this video render so well from doing it on so many different sbc`s that I recognize the paterns, (Also not scientific)
In video rendering it seems to use as much memory. But 32-bit seems quite a bit faster than 64-bit.
XU4 and Tinker Board as example.
But its like comparing raspberry
s with oranges (I hate Apple`s…)
XU4 = 46m23s
Tinker = 1h12m15s
C2 = 1h43m46
Thats a big gap with the 64-bit
s.
Too bad the XU4 isn`t power efficient, and the Tinker is just a big pile of shht.
I`ll do more tests now, thanks.
First test results.
It didnt use as much ram this time. Last time I had done a lot of tweaking before doing the render, maybe because of that there was more ram used. Also on the last image you see that the big bump at the end is while finishing the file. Here before I started Kdenlive with all the stats running. I didn
t turn on the fan yet there.
The first minutes.
Here it`s halfway. There it slows down just like the Khadas, and then goes on strong again.
Last 10%. Here it starts going very slow. This part takes a very long time.
Here almost finished.
This is the big bump where it writes the file. That
s what you
ve seen on that earlier picture. But it did use less memory.
As last. Here you see how long it did over that last bit. When it
s running well it
s about 53C. On the last part it
s only 42C. Over what should be 7 minutes it did 37minutes. I don
t know how to interpret all these numbers. I see that the load is lower, but why I don`t know.
Now did it with 6 threads(but all cores on).The same behaviour.
Time was : 1h24m29s
Only 38 seconds slower. That seems weird.
Thanks for the help