You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
When using the Semgrep LSP in large Git repositories that have many contributors (>1,000) and files, the Git operations that are ran by the LSP cause some very high CPU usage spikes every few seconds.
To Reproduce
Run the LSP and observing the CPU usage in a very large repo. Expected behavior
If only_git_dirty is set to false in the LSP settings, I'd expect that no Git operations would be run by the LSP which would resolve this issue.
Screenshots What is the priority of the bug to you?
We've currently disabled the Semgrep LSP because of this behaviour.
P0: blocking your adoption of Semgrep or workflow
P1: important to fix or quite annoying
P2: regular bug that should get fixed
Environment
If not using semgrep.dev: are you running off docker, an official binary, a local build?
The Semgrep LSP binary.
Use case
What will fixing this bug enable for you?
Allow us to re-enable the Semgrep LSP.
The text was updated successfully, but these errors were encountered:
Describe the bug
When using the Semgrep LSP in large Git repositories that have many contributors (>1,000) and files, the Git operations that are ran by the LSP cause some very high CPU usage spikes every few seconds.
To Reproduce
Run the LSP and observing the CPU usage in a very large repo.
Expected behavior
If
only_git_dirty
is set to false in the LSP settings, I'd expect that no Git operations would be run by the LSP which would resolve this issue.Screenshots
What is the priority of the bug to you?
We've currently disabled the Semgrep LSP because of this behaviour.
Environment
If not using semgrep.dev: are you running off docker, an official binary, a local build?
The Semgrep LSP binary.
Use case
What will fixing this bug enable for you?
Allow us to re-enable the Semgrep LSP.
The text was updated successfully, but these errors were encountered: