Scaling down the update frequency on the traffic graphs seems to
meaningfully reduce utilization. Many other widgets don't appear to
have have settings for their poll intervals. Are there other settings
hidden away reduce the update frequency (to prolong the suitability of
older hardware)?
I know that old routers have to meet their makers eventually, but I hate
to do so only because dashboard starts causing real-time applications to
fall over.
-K
On 6/23/2016 4:35 PM, Chris Buechler wrote:
On Thu, Jun 23, 2016 at 11:55 AM, Karl Fife <[email protected]> wrote:
Ever since upgrading to 2.3, I notice that the CPU utilization is uncommonly
high when a browser is pointed at the Status / Dashboard.
Naturally, this is the php-fpm process. Each instance of php-fpm runs at
between 8 and 40% of my 1.8ghz Atom (dual core, HT). With four or five
dasbord windows open and I can burn 70% of the CPU on the idle box. Doing
the same on <= 2.2 barely registers additional utilization.
Many more things dynamically update than before, and do so more often.
Opening up 5 dashboard instances basically turns the box into a
relatively busy web server, doing probably a few dozen requests per
second depending on which all widgets are enabled. Yes that will chew
some CPU on an old Atom.
_______________________________________________
pfSense mailing list
https://lists.pfsense.org/mailman/listinfo/list
Support the project with Gold! https://pfsense.org/gold
_______________________________________________
pfSense mailing list
https://lists.pfsense.org/mailman/listinfo/list
Support the project with Gold! https://pfsense.org/gold
