started test with previously disabled 2 big lists (in addition to my 70+), so fully loaded (5.7mio entries all in all):
whole process (pihole upgrade, list upgrade to building new gravitiy) took from
16:36 - 16:57 - 21 mins
mem just fine - 96MB system swap used after process completed
Now on gravity-test temporarily and updates are back to normal times, and metrics like cpu, scheduling, memory, disk are also back to normal. It also appears to have cleared the database readonly errors I was getting.
Not sure why 5.16.2 not showing up when trying to check for update - is there some specific option i need to use?
21:34:13-pi@dnspi3b:~ $pihole -up --check-only
[✓] Update local cache of available packages
[i] Existing PHP installation detected : PHP version 7.4.33
[✓] Checking for git
[✓] Checking for iproute2
[✓] Checking for dialog
[✓] Checking for ca-certificates
[i] Checking for updates...
[i] Pi-hole Core: update available
[i] Web Interface: update available
[i] FTL: update available
21:34:29-pi@dnspi3b:~ $pihole -v
Pi-hole version is v5.15.5 (Latest: v5.16.1)
AdminLTE version is v5.18.4 (Latest: v5.19)
FTL version is v5.21 (Latest: v5.2
Unfortunately, it is a bit more tricky than that. Reason is v6.0 which relies on the messages being generated solely by FTL so API calls to /api/info/messages do not really have to connect to the database but can use internal buffers to provide this. I'm not sure what is the best strategy right now, probably we have to do this and then we have to give up on this simplification in FTL.