Why does my Droplet show high CPU usage even when my app is idle?

Hi there,

This is almost never a DigitalOcean issue, and it is actually a pretty common thing to run into on fresh Droplets. A few things to check:

To find what is actually eating CPU run:

top -o %CPU

Sort by CPU and watch for a few seconds. If it is not your Node process, it is likely one of these culprits:

• unattended-upgrades running in the background on a fresh Ubuntu install
• systemd-journald doing log cleanup
• node itself leaking memory and triggering garbage collection constantly

For Node specifically, idle CPU spikes usually mean one of two things: a setInterval or background task you forgot about, or a memory leak forcing frequent GC cycles. Run this and watch memory over a few minutes:

watch -n 2 'ps aux --sort=-%mem | head -5'

Also check for crypto miners. Compromised Droplets are a real thing, especially if you left a port open or used a weak password. Look for unfamiliar process names in top.

If you share what process is showing high CPU in top, easier to point you in the right direction.

Heya, @9e483d26583f44f6bafe369a29b405

Not normal, but pretty easy to track down. The monitoring graphs show you that it’s high but top will show you what’s causing it.

Run top and press P to sort by CPU - whatever’s at the top is your culprit. If it’s your Node process, run top -H -p $(pgrep node) to see which thread is spinning.

A few common causes for idle Node apps eating CPU:

Polling loops or setInterval running too frequently, AI/LLM related stuff (you tagged AI Agents) doing background processing or keeping connections warm, a dependency doing something unexpected like a file watcher, or PM2/monitoring agent overhead if you’re running those.

Also worth checking htop if installed - gives a cleaner per-process view. And ps aux --sort=-%cpu | head for a quick snapshot.

What does the top process show when you run it?

Regards