What do you think of this module?

like other folks I’ve read comments from here, I too have turned my A06 Devterm into a CM4 device

I have the opposite experience: the CM4 is sluggish and I almost only ever use my A06 (really nice performance) or R01 (runs 6-8 hours and “not fast enough for a browser besides w3m/lynx” turns out to be a benefit). I have the CM4 in my uConsole and it’s fine but the A06 is speedy and works fine for me. (I even sprang for the 8GB CM4.) I ended up putting the CM4 into a module and slotting it into the TPi to use as a NAS.

it generally ran too hot to use them all

I think the big piece of copper and thermal paste came with later orders, or at least mine came with one; mine gets hot when it’s cranked all the way up but I rebuilt everything on-device except qt webengine (because it required more RAM to link than I could muster even after plugging in extra USB drives to use as swap). All the cores maxed out, it got up to 71C, kinda hot but still fine.

It’s possible I never got my scheduler and gear-shifting settings just right

I think what was helpful for me was I keep conky on the side (ratpoison with set padding 280 0 0 0, but I set it to toggle so I can hide conky if I want the rest of the screen), so I can see what’s going on and shift appropriately. I usually keep it cranked all the way down (-s 1 or -s 2) and turn it up when I am compiling something or if I attempt to use Firefox or mplayer or something starts to eat a lot of CPU. It’s on -s 1 right now, so just the ambient X/conky/ssh/drawterm stuff eats 13%, but it still lasts a long time. I tried to attach my .conkyrc but it’s not an allowed file type so here’s a screenshot and a gist The .conkyrc I am using on my DevTerm. · GitHub . Anyway, long way of saying it’s easier to figure out when you need to crank the gears up or down when you have a CPU monitor running.

As far as performance, I did some test compiles, the performance cores are about twice as fast at the same clock rate.