106
21.1 Legacy Series / Re: High CPU usage with flowd_aggregate.py ... IPv6 is disabled ... any ideas?
« on: June 29, 2021, 04:18:18 am »
A few things that would be worth mentioning.
1) If PowerD is not enabled, that doesn't necessarily mean your CPU is clocking to the highest speed. BSD has some pretty odd hardware support so I would actually recommend enabling PowerD and see if this allows the processor to turbo boost during high load, single thread scenarios like what we have here. The HiAdaptive profile is very good at these use cases.
2) The FlowD script that uses CPU on my OPNsense install is not due to RRD graphing, but the Netflow collection used for the 'Insight' page under the Reporting section of the OPNsense UI. I've seen where sometimes I have disabled the services (deselect all interfaces, uncheck local logging) and just hitting "apply" doesn't always completely disable it. I've had to reboot to fully get it stopped after I've de-selected all the interfaces on the Netflow config page. So if you haven't already, I would do a reboot after you've done this just to ensure it's fully off.
3) If you want to identify what is launching the process, a quick and dirty way to check is to watch the output of 'top -aSCHIP' in an SSH session. This will show you the full path that is launching the process, and will sort the highest CPU consuming processes on the top. Watch and wait for the flowd process to climb up the list and take a screenshot. It will look something like the screenshot I've posted here (which is a temporary CPU blip that I commonly see with FlowD in my environment, a small spike to 99% and then it drops back down after a few seconds).
1) If PowerD is not enabled, that doesn't necessarily mean your CPU is clocking to the highest speed. BSD has some pretty odd hardware support so I would actually recommend enabling PowerD and see if this allows the processor to turbo boost during high load, single thread scenarios like what we have here. The HiAdaptive profile is very good at these use cases.
2) The FlowD script that uses CPU on my OPNsense install is not due to RRD graphing, but the Netflow collection used for the 'Insight' page under the Reporting section of the OPNsense UI. I've seen where sometimes I have disabled the services (deselect all interfaces, uncheck local logging) and just hitting "apply" doesn't always completely disable it. I've had to reboot to fully get it stopped after I've de-selected all the interfaces on the Netflow config page. So if you haven't already, I would do a reboot after you've done this just to ensure it's fully off.
3) If you want to identify what is launching the process, a quick and dirty way to check is to watch the output of 'top -aSCHIP' in an SSH session. This will show you the full path that is launching the process, and will sort the highest CPU consuming processes on the top. Watch and wait for the flowd process to climb up the list and take a screenshot. It will look something like the screenshot I've posted here (which is a temporary CPU blip that I commonly see with FlowD in my environment, a small spike to 99% and then it drops back down after a few seconds).