03-20-2021, 01:39 PM
(03-20-2021, 03:28 AM)Tim Curtis Wrote: I have a "no j4" version the update on the distribution server but it will require some tweaks to point to it from your 3A+.
Email or PM me tomorrow and we can test it out.
Sure I can test it but here's what I've already found by running just STEP 7-9 in isolation. [I screwed up the script though, so I didn't capture your nice log output with time stamps.]
moOde 7.1.0 ('cuz I'd already updated), no swap
With 'make -j4' replaced by 'make', the upmpdcli (Src 1-2) portion compiled quickly. There was always at least 200MiB of available memory and cc1plus was often the most active process.
However, the libupnpp-bindings (Src 2-2) portion is still grinding on, 50m into my test.
It's stuck in building libs/upnpp_wrap.o at the moment. We're down to ca 60MiB available memory (the scheduler has had to dip into the buff/cache reserve) and the most active process is the dreaded kswapd0. Basically we're just thrashing. All 4 CPUs are mostly in the wait state with some percentage of idle state and almost no percentage in user state. The desired cc1plus process is getting between 0% and 2% of CPU.
I really think enabling swap for the duration of the update is the better solution. I'll test it later with the RPi Zero-W I just pulled out of its hiding place.
Regards,
Kent
