🐛 Very aggressive CPU usage when switching branches on Biome 2.0

[walkerdb]

IDE and version

WebStorm 2025.1.3

Extension version

1.7.2

Biome version

2.0.5

Operating system

• Windows
• macOS
• Linux

Description

Any time I change branches now that we're on Biome 2.x the biome process takes up 100% CPU for multiple seconds, presumably doing some kind of full-filesystem-scan? We don't use any project rules so I'm confused why it's doing this work at all.

We're working on a very large monorepo, presumably total number of files under Biome's purview has something to do with it.

Steps to reproduce

1. change branches
2. watch biome CPU usage skyrocket

Expected behavior

Changing branches while my IDE is open does not result in huge CPU usage due to Biome.

Does this issue occur when using the CLI directly?

Not sure / Not applicable

Link to a minimal reproduction

No response

[github-actions]

Hello @walkerdb, please provide a minimal reproduction. You can use one of the following options:

• Provide a link to our playground, if it's applicable.
• Provide a link to GitHub repository. To easily create a reproduction, you can use our interactive CLI via npm create @biomejs/biome-reproduction

Issues marked with S-Needs repro will be closed if they have no activity within 3 days.