Actions
Bug #17767
closed
Do a `git gc` periodically
Status:
Released
Priority:
N/A
Assignee:
Category:
Performance and scalability
Target version:
Pull Request:
Severity:
Major - prevents use of part of Rudder | no simple workaround
UX impact:
User visibility:
Operational - other Techniques | Rudder settings | Plugins
Effort required:
Priority:
43
Name check:
To do
Fix check:
To do
Regression:
Description
We have several cases where git becomes extremely slow, with git status taking tens of seconds to finish. This is because jgit doesn't periodically do git gc and garbage accumulate.
We should do a git gc periodically, perhaps once a week, or at each rudder boot.
I put that in 5.0 as it is a bug, but depending of complexity it may end in 6.0 or 6.1.
Updated by François ARMAND over 4 years ago
- Category changed from Web - Maintenance to Performance and scalability
- Severity set to Major - prevents use of part of Rudder | no simple workaround
- User visibility set to Operational - other Techniques | Rudder settings | Plugins
- Priority changed from 0 to 52
Setting to major, because it's very hard to understand why rudder is starting to fail and be slow.
Updated by
Updated by François ARMAND over 3 years ago
- Target version changed from 6.1.17 to 7.0.0~beta3
Finally, we will had it in in rudder 7.0. It could be backported if necessary.
Updated by François ARMAND over 3 years ago
- Status changed from In progress to Pending technical review
- Assignee changed from François ARMAND to Vincent MEMBRÉ
- Pull Request set to https://github.com/Normation/rudder/pull/3984
Updated by François ARMAND over 3 years ago
- Status changed from Pending technical review to Pending release
Applied in changeset rudder|a184c049ea979bbabd5ce814902d8a42ff32ae4b.
Updated by Vincent MEMBRÉ over 3 years ago
- Status changed from Pending release to Released
This bug has been fixed in Rudder 7.0.0~beta3 which was released today.
Actions