24.11 on SG-2100 first impression (and issues)
-
@Cabledude said in 24.11 on SG-2100 first impression (and issues):
I go to Menu / Diagnostics / Command Prompt, type "top -HaSP" in the Execute Shell Command box and click Execute.
Ah OK. That's not the CLI (command line interface). I meant to run that command at the real command prompt so either via SSH or using the console directly. The command prompt page in the webgui is only for commands with a static output. And in fact anything run using the webgui uses significant CPU by itself.
-
@stephenw10 Ah I see. Never used CLI except wired. I enabled SSH since I had to learn sometime
This is what I get, without dashboard opened or active:
last pid: 76645; load averages: 0.56, 0.49, 0.40 up 0+06:10:24 18:26:22 258 threads: 3 running, 236 sleeping, 19 waiting CPU 0: 18.6% user, 0.0% nice, 9.1% system, 5.9% interrupt, 66.4% idle CPU 1: 21.4% user, 0.0% nice, 9.1% system, 5.9% interrupt, 63.6% idle Mem: 170M Active, 251M Inact, 506M Wired, 2371M Free ARC: 199M Total, 78M MFU, 112M MRU, 770K Anon, 1406K Header, 7176K Other 159M Compressed, 424M Uncompressed, 2.67:1 Ratio PID USERNAME PRI NICE SIZE RES STATE C TIME WCPU COMMAND 11 root 187 ki31 0B 32K RUN 0 306:59 64.97% [idle{idle: cpu0}] 11 root 187 ki31 0B 32K CPU1 1 302:40 64.56% [idle{idle: cpu1}] 97139 unbound 55 0 137M 113M kqread 1 0:20 32.05% /usr/local/sbin/unbound -c /var 97139 unbound 52 0 137M 113M kqread 0 0:16 23.78% /usr/local/sbin/unbound -c /var 12 root -64 - 0B 272K WAIT 1 4:25 2.43% [intr{gic0,s45: mvneta1}] 12 root -64 - 0B 272K WAIT 0 3:12 2.09% [intr{gic0,s42: mvneta0}] 12 root -60 - 0B 272K WAIT 1 2:23 1.97% [intr{swi1: netisr 1}] 12 root -60 - 0B 272K WAIT 0 3:23 1.88% [intr{swi1: netisr 0}] 2 root -60 - 0B 32K WAIT 0 4:13 1.38% [clock{clock (0)}] 0 root -12 - 0B 992K - 1 2:06 1.03% [kernel{z_wr_iss}] 94582 root 20 0 19M 9584K kqread 1 0:15 0.91% /usr/local/sbin/lighttpd_pfb -f 0 root -16 - 0B 992K - 1 0:42 0.56% [kernel{z_wr_int}] 12 root -64 - 0B 272K WAIT 1 0:25 0.49% [intr{gic0,s27: ahci0}] 36084 SPK 20 0 14M 4424K CPU0 0 0:01 0.46% top -HaSP 4 root -16 - 0B 48K - 1 0:15 0.40% [cam{doneq0}] 76679 avahi 20 0 14M 4524K select 1 1:25 0.17% avahi-daemon: running [SPK.loca 0 root -16 - 0B 992K - 1 0:03 0.16% [kernel{z_null_int}] 0 root -16 - 0B 992K - 1 0:02 0.12% [kernel{z_flush_int}] 7 root -16 - 0B 16K pftm 1 0:37 0.11% [pf purge] 20652 SPK 20 0 22M 11M select 1 0:00 0.09% sshd: SPK@pts/0 (sshd)Looking at this output and seeing the cpu is largely idle and any significant usage is down to pfBlocker, I must assume that the high cpu I get with dashboard open is caused by the new dashboard widget build in 24.11.
I made a short video showing the "top -HaSP" command CLI output with/without dash open. It's 1.3MB in size.
Not sure how I can make the video available to you though.Takeaway is it's mostly idle now with dash off:
last pid: 28321; load averages: 0.30, 0.33, 0.40 up 0+06:29:57 18:45:55 258 threads: 3 running, 236 sleeping, 19 waiting CPU 0: 0.0% user, 0.0% nice, 1.2% system, 1.6% interrupt, 97.3% idle CPU 1: 0.0% user, 0.0% nice, 0.8% system, 0.8% interrupt, 98.4% idle Mem: 197M Active, 233M Inact, 493M Wired, 2375M Free ARC: 199M Total, 78M MFU, 113M MRU, 276K Anon, 1406K Header, 7113K Other 159M Compressed, 425M Uncompressed, 2.68:1 Ratio PID USERNAME PRI NICE SIZE RES STATE C TIME WCPU COMMAND 11 root 187 ki31 0B 32K CPU1 1 318:59 98.50% [idle{idle: cpu1}] 11 root 187 ki31 0B 32K RUN 0 323:28 97.43% [idle{idle: cpu0}] 2 root -60 - 0B 32K WAIT 0 4:27 1.15% [clock{clock (0)}] 12 root -64 - 0B 272K WAIT 1 4:39 0.83% [intr{gic0,s45: mvneta1}] 12 root -60 - 0B 272K WAIT 0 3:33 0.79% [intr{swi1: netisr 0}] 47523 SPK 20 0 14M 4848K CPU0 0 0:03 0.40% top -HaSP 12 root -64 - 0B 272K WAIT 0 3:19 0.15% [intr{gic0,s42: mvneta0}] 76679 avahi 20 0 14M 4524K select 0 1:30 0.13% avahi-daemon: running [SPK.loca 7 root -16 - 0B 16K pftm 1 0:38 0.10% [pf purge] 12 root -60 - 0B 272K WAIT 1 2:29 0.08% [intr{swi1: netisr 1}] 20652 SPKSo I suppose the unit is doing fine now with 24.11, only the dash widget refresh is problematic. Might be better on the intel models such as 4100 4200 6100 etc. but I wanted the ultimate low power firewall...
-
I mean Unbound usage there is expected. Nothing there really looks like an issue.
I would try that patch I linked to. That should help with widget refreshes on the dashboard using CPU.
-
@stephenw10 said in 24.11 on SG-2100 first impression (and issues):
I mean Unbound usage there is expected. Nothing there really looks like an issue.
I agree, I had that feeling myself too, when I wrote it's doing fine now, but I appreciate your opinion because you're the master 8-)
I would try that patch I linked to. That should help with widget refreshes on the dashboard using CPU.
I appreciate the link, I reverted and now the cpu in the dashboard page is much lower, but the number updates only every 30 seconds, where before it was more like between 5-8 seconds.
Do you reckon more work will be done on the widget refresh engine? So that it will perform on the ARM units like 24.03 and before?
-
@Cabledude :)
@SteveITS said in 24.11 on SG-2100 first impression (and issues):
25.03 will have a fix also. https://docs.netgate.com/pfsense/en/latest/releases/25-03.html#dashboard
-
Yes it's better in 25.03
-
@SteveITS said in 24.11 on SG-2100 first impression (and issues):
@Cabledude said in 24.11 on SG-2100 first impression (and issues):
on LAN1 and VLAN10 and the subnets are identical
Hm, normally that's a problem for pfSense in that it won't know where to route those packets.
Apologise for the massive delay. I meant identical before/after moving from 24.03 to 24.11
-
@stephenw10 said in 24.11 on SG-2100 first impression (and issues):
Yes it's better in 25.03
Hi Steve,
I am still on 24.11 for my 2100 Max and I can’t escape the feeling the UI is substantially more sluggish than on 24.03. I cant list any specific tasks right now but the experience is bad. Many tasks can take so long (like 10 seconds or more for setting a static IP for a DHCP client) I start wondering if the system hangs, but then every time it completes normally but it takes too long for comfort. For the first time I start regretting the ARM, wishing I’d gone with one of the higher priced intel models.Can you confirm this is happening with 24.11 on the ARM models? And is the trouble over after moving to 25.03.
Thanks,
Pete -
I can't confirm anything specific, I'm not really seeing that here. In the 25.07 the dashboard widget update behaviour is improved which is what most people were hitting in 24.11.
-
@Cabledude FWIW leaving the dashboard open is also going to log every HTTP request for updating said dashboards. (disk writes)
Watch your CPU usage without the dashboard open, and while you make the DHCP changes (e.g. "top" command line).
