Repo indexer is a memory hog #2259

New Issue

2025-11-02T04:29:57-06:00

GiteaMirror commented

2025-11-02 04:29:57 -06:00

Originally created by @mvrhov on GitHub (Aug 28, 2018).

Gitea version (or commit ref): 1.5.0
Git version: 2.18
Operating system: Ubuntu Xenial
Database (use [x]):
- PostgreSQL
- MySQL
- MSSQL
- SQLite
Can you reproduce the bug at https://try.gitea.io:
- Yes (provide example URL)
- No
- Not relevant
Log gist:

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

Server Uptime    6 minutes, 18 seconds
Current Goroutines    31
Current Memory Usage    1.4GB
Total Memory Allocated    23GB
Memory Obtained    1.8GB
Pointer Lookup Times    10848
Memory Allocations    184233578
Memory Frees    175630887
Current Heap Usage    1.4GB
Heap Memory Obtained    1.7GB
Heap Memory Idle    276MB
Heap Memory In Use    1.4GB
Heap Memory Released    0B
Heap Objects    8602691

The same but with repo indexer turned off:

Server Uptime    6 minutes, 20 seconds
Current Goroutines    26
Current Memory Usage    20MB
Total Memory Allocated    140MB
Memory Obtained    69MB
Pointer Lookup Times    822
Memory Allocations    482121
Memory Frees    298375
Current Heap Usage    20MB
Heap Memory Obtained    62MB
Heap Memory Idle    38MB
Heap Memory In Use    25MB
Heap Memory Released    0B
Heap Objects    183746

There is ~ 50 repos which totals approximately ~500MB in size

Originally created by @mvrhov on GitHub (Aug 28, 2018). - Gitea version (or commit ref): 1.5.0 - Git version: 2.18 - Operating system: Ubuntu Xenial - Database (use `[x]`): - [X] PostgreSQL - [ ] MySQL - [ ] MSSQL - [ ] SQLite - Can you reproduce the bug at https://try.gitea.io: - [ ] Yes (provide example URL) - [ ] No - [X] Not relevant - Log gist: ## 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 ``` Server Uptime 6 minutes, 18 seconds Current Goroutines 31 Current Memory Usage 1.4GB Total Memory Allocated 23GB Memory Obtained 1.8GB Pointer Lookup Times 10848 Memory Allocations 184233578 Memory Frees 175630887 Current Heap Usage 1.4GB Heap Memory Obtained 1.7GB Heap Memory Idle 276MB Heap Memory In Use 1.4GB Heap Memory Released 0B Heap Objects 8602691 ``` The same but with repo indexer turned off: ``` Server Uptime 6 minutes, 20 seconds Current Goroutines 26 Current Memory Usage 20MB Total Memory Allocated 140MB Memory Obtained 69MB Pointer Lookup Times 822 Memory Allocations 482121 Memory Frees 298375 Current Heap Usage 20MB Heap Memory Obtained 62MB Heap Memory Idle 38MB Heap Memory In Use 25MB Heap Memory Released 0B Heap Objects 183746 ``` There is ~ 50 repos which totals approximately ~500MB in size

GiteaMirror added the issue/confirmed type/enhancement labels 2025-11-02 04:29:57 -06:00

GiteaMirror closed this issue

2025-11-02 04:29:57 -06:00

GiteaMirror commented

2025-11-02 04:29:58 -06:00

@sps-jlwalker commented on GitHub (Nov 6, 2018):

I've encountered something similar on Windows as well. Gitea crashes once the indexer grows too large.

@sps-jlwalker commented on GitHub (Nov 6, 2018): I've encountered something similar on Windows as well. Gitea crashes once the indexer grows too large.

GiteaMirror commented

2025-11-02 04:29:59 -06:00

@lafriks commented on GitHub (Nov 6, 2018):

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)

@lafriks commented on GitHub (Nov 6, 2018): 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)

GiteaMirror commented

2025-11-02 04:29:59 -06:00

@lunny commented on GitHub (Nov 7, 2018):

Maybe related with #4450 ?

@lunny commented on GitHub (Nov 7, 2018): Maybe related with #4450 ?

GiteaMirror commented

2025-11-02 04:29:59 -06:00

@mvrhov commented on GitHub (Nov 7, 2018):

It definitely not related!

@mvrhov commented on GitHub (Nov 7, 2018): It definitely not related!

GiteaMirror commented

2025-11-02 04:30:00 -06:00

@stale[bot] commented on GitHub (Jan 6, 2019):

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.

@stale[bot] commented on GitHub (Jan 6, 2019): 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.

GiteaMirror commented

2025-11-02 04:30:00 -06:00