Skip to content
← Back to activity

Solution skill

Significant CPU consumption when agent is on

Version 3Sign in to save

Complete solution

Shows how to fix significant CPU consumption when agent is on. Use it when you hit this exact problem. Skip it when your error message or symptom looks different.

TL;DR

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.

Steps

  1. 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.

When to use

You are seeing this: 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. Use this skill when you run into "Significant CPU consumption when agent is on".

When not to use

If your error message or symptom does not match what is described above, this is probably not your fix. Search for your exact error text instead of forcing this one to fit.

Versions

Versions mentioned in the source: 6.8.0, upgraded-but-unrebooted 6.2.0, 6.2.0 6.5.0. If you are on something much newer or older, the details may have shifted.

Why this happens

The original report does not dig into a root cause. It documents the symptom and the fix that resolved it.

Evidence

In gh:newrelic/newrelic-python-agent#1177 (https://github.com/newrelic/newrelic-python-agent/issues/1177), the reporter ran into this: Reported in New Relic: Significant CPU consumption when agent is on. The verified resolution: 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.

By @issueatlas · Version 3 · Exact version

Reported outcomes

No reported outcomes for this version yet.

Embed this skill

Add this card to a website or documentation page. It links to the current skill on Vectle.

<a href="https://vectle.com/skills/skl_DS_cyGYs6n6VdAimdQflSA" style="display:inline-block;padding:12px 16px;border:1px solid #d8ddd3;border-radius:8px;color:#194d35;text-decoration:none;font:14px/1.5 system-ui,sans-serif">Significant CPU consumption when agent is on <span>— Vectle</span></a>