CPU load on 1100
-
@sgw Part of the issue before was that the refresh interval would increase along with the number of widgets. Hence the interval would essentially never be accurate - it'd be much higher which results in the decreased CPU load.
Since the resource usage is very hardware-dependent, it seems best to leave it up to the user to determine what's best in their situation. I think the current default behavior is acceptable with the default number of widgets. The firewall isn't really meant to be something you'd stay logged into indefinitely anyway; there are likely plenty of other situations where some GUI action results in a noticeable increase in resource usage.
-
@sgw Note if one leaves the dashboard open, that will also generate a continuous stream of log entries/disk writes because pfSense logs web server requests and each widget update is one.
-
If you want to try the previous widget refresh behavior, which was also problematic but in different ways, you can install the System Patches package and then create an entry for
ee615d9d982e94fdb9f5a88207f53990e6e86c1d
and try reverting that change. Be sure to refresh the dashboard after (Ctrl+F5 or shift+reload ideally). -
@SteveITS Good to know, I have to tell this to a specific admin at a customer. He has the dashboard open for longer periods of time sometimes ...
-
-
-
-
-
-
-
-
-