Skip to content

docs: explain language insights and config mechanisms #280

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

Merged
merged 2 commits into from
Apr 26, 2024

Conversation

bahrmichael
Copy link
Contributor

This PR updates the documentation as a follow-up to https://github.com/sourcegraph/sourcegraph/pull/62011 where we introduced new environment variables and improved the performance of language stats insights.

Copy link

vercel bot commented Apr 26, 2024

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name Status Preview Comments Updated (UTC)
sourcegraph-docs-v2 ✅ Ready (Inspect) Visit Preview 💬 Add feedback Apr 26, 2024 9:30am

Comment on lines +76 to +97
### Concurrent Requests

This concurrent requests to the gitserver are configurable through the `GET_INVENTORY_GIT_SERVER_CONCURRENCY` environment variable ([#62011](https://github.com/sourcegraph/sourcegraph/pull/62011)).
We recommend increasing this carefully, as an increase in concurrency may cause the gitserver to become overloaded and slow down responses.

Example:

```
GET_INVENTORY_GIT_SERVER_CONCURRENCY=4
```

To understand how this configuration impacts your language stats queries you can use [tracing](/admin/observability/tracing).

### Language Stats Timeout

The timeout in minutes for language stats queries is configurable through the `GET_INVENTORY_TIMEOUT` environment variable ([#62011](https://github.com/sourcegraph/sourcegraph/pull/62011)).

Example:

```
GET_INVENTORY_TIMEOUT=5
```
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'm not positive we want to be advertising these env vars. Generally, env vars are so we can have escape hatches in case of emergency, but we don't really want customers to be messing with them without help from support. I think it's probably fine to leave this section with the "reach out to Sourcegraph support"

Copy link
Contributor Author

@bahrmichael bahrmichael Apr 30, 2024

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

If we drop the section here, I'd like to figure out a place where our support engineers can discover this info by themselves. Where would we document this for our support folks?

@bahrmichael bahrmichael merged commit 19e5617 into main Apr 26, 2024
@bahrmichael bahrmichael deleted the bahrmichael/62011-docs-update branch April 26, 2024 16:30
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants