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

BUG: File History Is An Order Of Magnitude Slow On Larger Repos #62601

Open
alexAtSourcegraph opened this issue May 10, 2024 · 1 comment
Open
Labels
bug An error, flaw or fault that produces an incorrect or unexpected result, or behavior. team/code-search Issues owned by the code search team

Comments

@alexAtSourcegraph
Copy link
Contributor

  • Sourcegraph version: 4.1.x
  • Platform information: Self-Hosted K8s

Steps to reproduce:

  1. Select a file within Sourcegraph Code Search within a repo that is ~5GB
  2. Select "History" for the file and wait for the commit history of the file to appear

Expected behavior:

The file history should appear within 1-3 seconds.

Actual behavior:

The file history appears within 30 seconds

If you would like immediate help on this, please email support@sourcegraph.com (you can still create the issue, but there are no SLAs on issues like there are for support requests).

@alexAtSourcegraph alexAtSourcegraph added team/code-search Issues owned by the code search team bug An error, flaw or fault that produces an incorrect or unexpected result, or behavior. labels May 10, 2024
@camdencheek
Copy link
Member

Hey @alexAtSourcegraph! Do you have any specific examples here? I'm happy to take a look to see if there was a regression, but file history can definitely be slow since we need to potentially iterate over many commits to find the ones that have changed the file we care about. This is a known issue, but not something that we expect to get better any time soon.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug An error, flaw or fault that produces an incorrect or unexpected result, or behavior. team/code-search Issues owned by the code search team
Projects
None yet
Development

No branches or pull requests

2 participants