The obfuscation process consumes available resources with a lower priority. If more important processes need CPU/Memory the obfuscation is de-prioritized or will wait until resources are available.
by the way, don't rely on Concurrent connections in your calculations , you have to monitor the Data plane itself on the ( Even-Cores ) and see it's percentage.
>> use TOP command script on Bigip bash prompit , and see which process consumes much of CPU or send a snap shot form Top Command if you wish.
In addition to what @Mohamed_Ahmed_Kansoh mentioned, if you're provisioning AVR module, it might cause high CPU utilization depending on how many virtual servers are using the analytics profile.
Also, the odd and even cores can be extracted from the CPU graph on ihealth portal. you can generate a new QKVIEW file, import it to any of your F5 accounts and navigate to "graphs" section. then, select "Blade 0 CPU Usage By Core" and filter by the even cores as Kansoh mentioned.
you can also try rebooting the device and check if the same CPU utilization occurring or not, because sometimes cleaning up files, and processes might hang out.
I'm afraid so, if you have a valid support contract with F5 support, you can open a case and check whether they could provide you with a hotfix or if it is still being analyzed with the development team.
@kgaigl , Could you please check the Data plane cores or go to >> Statictics ---> dashboard .
you can see the data plane and control clearly.
> also , did you issue Top command or not ? we need to see if your bigip triggered idle enforcer mode or not , or check the process that consumes that CPU.
The obfuscation process consumes available resources with a lower priority. If more important processes need CPU/Memory the obfuscation is de-prioritized or will wait until resources are available.
Yes , I expected that too from the graphs , it follows the same trend everyday , which me some tasks or processes runing in the background. So it was the ASM Obfuscator
If you found @Mohamed_Ahmed_Kansohs' reply matches your issue and the root cause, please accept his response as a solution to help others find the solution faster.
