Closed Bug 1667041 Opened 4 years ago Closed 4 years ago

Do not consume all cores when indexing C++ with clangd

Categories

(Developer Infrastructure :: Developer Environment Integration, enhancement)

enhancement

Tracking

(firefox83 fixed)

RESOLVED FIXED
83 Branch
Tracking Status
firefox83 --- fixed

People

(Reporter: andi, Assigned: andi)

References

(Blocks 1 open bug)

Details

Attachments

(1 file)

When using clangd with vscode we shouldn't consume all available cores for indexing TU and it's includes, a better approach would be to consume only half of them.

(In reply to Andi-Bogdan Postelnicu [:andi] from comment #0)

When using clangd with vscode we shouldn't consume all available cores for indexing TU and it's includes, a better approach would be to consume only half of them.

Why? clangd sets itself to have a low priority.

I tried this morning to open js/src/vm/Runtime.h with clangd and it uses all CPU to the point that spotify wasn't playing music anymore :p

Maybe changing the priority could be enough?

It's the same on windows, let's make this more conventional and use less cpu cores.

Pushed by bpostelnicu@mozilla.com:
https://hg.mozilla.org/integration/autoland/rev/07835afc964c
Do not consume all cores when indexing C++ with `clangd` from `vscode`. r=sylvestre
Status: NEW → RESOLVED
Closed: 4 years ago
Resolution: --- → FIXED
Target Milestone: --- → 83 Branch
Product: Firefox Build System → Developer Infrastructure
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Creator:
Created:
Updated:
Size: