its been about 1 day since I made the changes posted in the pull request and thus far have no issues with snmp causing slow downs. it still is typically at the top of cpu usage (10-15%) but never near the 100% + unresponsive console/gui that existed
For me it was the Hoobs jail that caused sysctl -a to consume >95% of one cpu.For me, stopping my 3 Jails cleared up the slowness… SSH and GUI would stall for > 60 seconds at a time.
sysctl was constantly > 95% on one cpu when using top.
70GB 0f 96GB RAM free and ARC only sitting at 10GB now after uptime of 10 mins.
ARC would normally grow to leave around 3GB free once it fills up servicing the 3 pools.
Services running:
SSHSMBZeroTierJails are:
NetdataHoobsQBittorrentAm happy to delete jails and rebuild them from scratch (bit annoying but not the end of the world) when I have more time.
I noticed I cannot change the train in the GUI for updates… Is this because there's no nightlies offered post 12.0-release yet?
the changes from the pull request only fix issues with 1) snmp service provided by truenas via snmp-agent.py and 2) debug logs with zfs config....I think.
anything else that does sysctl -a or even sysctl kstat.zfs will have a bad time. there is a CTLFLAG_SKIP under SYSCTL(9) so I guess you could write a kernel module that skips the problematic entries and load that...assuming that SYSCTL(8) honors that flag which...um...I cant tell from just a quick search.
First of all, as FrankNAS pointed out, the pull requests may only help depending on what you're running.Can you tell me how to actually make those sysctl changes from the pull request? I don't know where to even begin.