Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

High Semgrep LSP CPU usage caused by recurring Git operations #10263

Open
1 of 3 tasks
tomasf-stripe opened this issue May 20, 2024 · 0 comments
Open
1 of 3 tasks

High Semgrep LSP CPU usage caused by recurring Git operations #10263

tomasf-stripe opened this issue May 20, 2024 · 0 comments

Comments

@tomasf-stripe
Copy link

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
image
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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Development

No branches or pull requests

2 participants