-
-
Notifications
You must be signed in to change notification settings - Fork 5.8k
Repo indexer is a memory hog #4807
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
Comments
I've encountered something similar on Windows as well. Gitea crashes once the indexer grows too large. |
Yes that is why it is marked as experimental feature. Once we have finished notification refactoring we should also refactor indexing to allow other source indexing options (googlecode search lib is one option, external elastic instance could be other) |
Maybe related with #4450 ? |
It definitely not related! |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs during the next 2 weeks. Thank you for your contributions. |
I think this has been resolved sometimes. I will close this and please feel free to reopen it. |
[x]
):Description
If one enables repo indexer to be able to search for a code the Gitea becomes a real memory hog.
This is the excerpt from the Dashboard with repo indexer on:
This of course goes on and on.. until the OS kills the app due to OOM
The same but with repo indexer turned off:
There is ~ 50 repos which totals approximately ~500MB in size
The text was updated successfully, but these errors were encountered: