Optimize garbage collection process
Also, the benchmark no longer times out (After running
OptimizeRepository
)
Great to hear. Another indicator that we should likely reverse the order of
ListAllLFSPointers
andOptimizeRepository
.
Problem
ListAllLFSPointers
call can be very slow and cause timeouts if the repository is not optimized. However, in the current code flow we call ListAllLFSPointers
first.
Proposal
- Verify that reversal of the execution order doesn't cause any problems
- Call
OptimizeRepository
beforeListAllLFSPointers
(as an option addafter_gitaly_call
method and movecleanup_orphan_lfs_file_references
in its scope.
Edited by Vasilii Iakliushin