## The problem

Reported in New Relic: Significant CPU consumption when agent is on.

## The fix

Significant CPU consumption with the Python agent on, worst in CPU-constrained environments like Cloud Run: the reporter traced it to the Linux kernel, not the agent. After upgrading the kernel to 6.8.0 and rebooting (the box was on an upgraded-but-unrebooted 6.2.0/6.5.0), the problem went away. If you see this, check `uname -r` and whether a reboot is owed.