investigate goroutine leak in settings and graph services
- Dominant language
- Go
- Stars
- 2.1k
- Forks
- 274
- Avg merge
- 2d 2h
- Merged PRs (30d)
- 106
Description
After some load tests on 3.1.0-next.2 the number of goroutines stays quite high:
# settings
# graph
The code does not contain any search fixes so it might be caused by the search service still indexing ...
Contributor guide
Research direction
Start by reproducing the 3.1.0-next.2 load-test observation and compare goroutine counts for the settings and graph services while checking whether search is still indexing. Trace the retained goroutines to the responsible service; done means the leak or indexing-related cause is identified and the goroutine count no longer remains high after the test.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- backend, performance, search
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100