CPU data, control and analytics plane utilization

Each CPU core is designated as data, control, or analytics, with all usage assigned to the core's designated category. Each even-numbered core is designated as a data plane, each odd-numbered core as a control plane, and the highest odd-numbered core as an analytics plane.

Analytics plane-related processes are typically pinned to the highest odd-numbered core, and no control or analytics processes have access to the even-numbered cores. The processes pinned to the analytics plane usually consume all available CPU cycles when running, which is why they are assigned to a single specific core.

This division occurs when the CPU supports Hyper-Threading Technology (HT Technology). Overview of the HTSplit feature - https://my.f5.com/manage/s/article/K23505424 

The BIG-IP VE system does not support this feature on generic hypervisors such as VMware ESX/i, where each vCPU will be allocated one TMM process.  https://my.f5.com/manage/s/article/K15468#tmsh 

If you are seeing control plane and data plane CPU statistics in the dashboard, this is related to bug I id 969329 - https://my.f5.com/manage/s/article/K000132982 

For some reason, I’m unable to upload the .zip file here in the post. Here’s the link with the script.