cpu utilizations is maxed out

Whenever I run superset especially 2.0 version it maxes out my CPU for some reason. Where do I look for it to debug it?

Thanks for the report! To help debug this, could you share a bit more detail? The report doesn't yet have enough specifics to reproduce or pinpoint a code path:

Version: You mention "2.0" — could you confirm the exact build from About Superset (e.g. 2.0.x)? V2 is still being rolled out, so the precise build matters.
OS & hardware: e.g. macOS 14.5 / Apple M2 / 16 GB RAM.
Number of workspaces open, and roughly how many terminals/agent sessions per workspace.
When the CPU spikes: at idle, while typing, while an agent session is running, after the app has been open for a while, etc.
Which process is maxed out in Activity Monitor / Task Manager — Superset (main), Superset Helper (Renderer), Superset Helper (GPU), or a child process like node/bash? A screenshot of the per-process breakdown is the most useful single artifact.
Sampling: on macOS, if it's the renderer that's hot, running sample <pid> 5 against that PID and pasting the top stacks would let us pin down which loop is burning CPU.

A few things that may already be relevant:

Reduce renderer polling for resource and terminal surfaces #4581 (just merged on main) reduced polling in the resource monitor, background terminals dropdown, and terminal session dropdown — these were known CPU offenders. If you can reproduce on a build that includes that change, please mention it.
CPU Performance issues in V2 #4412 tracks general V2 CPU usage with many workspaces open.
feat(desktop): reduce EDR/security agent CPU usage from idle terminals and active agent sessions #3235 covers EDR/security agent CPU from idle terminals.
[perf] Severe input lag from excessive git subprocesses across all open workspaces #4198 covers input lag from excessive git subprocesses across open workspaces.

If any of those match your symptoms, a comment on that thread with your repro details would help consolidate the investigation. Otherwise the details above will let us narrow down a specific subsystem to instrument.

Hi there, apologies! The best thing to do is to probably sample the processes that are clobbering your cpu - you can do this in the activity monitor. Once you've sampled, you can send the file over and we'll investigate. Thanks in advance!

Sample of Superset.txt

here you go.

I am having the same issue since since version 1.9+ it's frustrating.

Apologies y'all, we're looking into it today!

I don's see CPU issues with latest 1.9.9

@saddlepaddle

Is this resolved guys? Superset is unusable right now @saddlepaddle @Kitenite

Hey we shipped 2 throttling improvements on heavier processes we were running. Is this still a big problem for you in latest?

this looks like this has been resolved

Navigation Menu

Repository navigation

cpu utilizations is maxed out #4634

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

cpu utilizations is maxed out #4634

Description

Activity

github-actions commented on May 16, 2026

saddlepaddle commented on May 16, 2026

hsetty commented on May 16, 2026

uditgoenka commented on May 18, 2026

saddlepaddle commented on May 18, 2026

vpetkovic commented on May 20, 2026

uditgoenka commented on May 21, 2026

Kitenite commented on May 21, 2026

hsetty commented on May 28, 2026

Metadata

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

Issue actions