2016-01-29 22:53:50 +05:30
# Housekeeping
2019-12-21 20:55:43 +05:30
> [Introduced](https://gitlab.com/gitlab-org/gitlab-foss/issues/3041) in GitLab 8.4.
2016-01-29 22:53:50 +05:30
2017-08-17 22:00:37 +05:30
## Automatic housekeeping
2016-01-29 22:53:50 +05:30
2017-08-17 22:00:37 +05:30
GitLab automatically runs `git gc` and `git repack` on repositories
2020-03-09 13:42:32 +05:30
after Git pushes. You can change how often this happens or turn it off in
**Admin Area > Settings > Repository** (`/admin/application_settings/repository`).
2016-01-29 22:53:50 +05:30
2017-08-17 22:00:37 +05:30
## Manual housekeeping
2020-03-09 13:42:32 +05:30
The housekeeping function runs `repack` or `gc` depending on the
**Housekeeping** settings configured in **Admin Area > Settings > Repository** .
2017-08-17 22:00:37 +05:30
For example in the following scenario a `git repack -d` will be executed:
2019-03-02 22:35:43 +05:30
- Project: pushes since gc counter (`pushes_since_gc`) = `10`
- Git GC period = `200`
- Full repack period = `50`
2017-08-17 22:00:37 +05:30
When the `pushes_since_gc` value is 50 a `repack -A -d --pack-kept-objects` will run, similarly when
the `pushes_since_gc` value is 200 a `git gc` will be run.
2019-12-21 20:55:43 +05:30
- `git gc` ([man page](https://mirrors.edge.kernel.org/pub/software/scm/git/docs/git-gc.html)) runs a number of housekeeping tasks,
2019-03-02 22:35:43 +05:30
such as compressing filerevisions (to reduce disk space and increase performance)
and removing unreachable objects which may have been created from prior invocations of
`git add` .
2019-12-21 20:55:43 +05:30
- `git repack` ([man page](https://mirrors.edge.kernel.org/pub/software/scm/git/docs/git-repack.html)) re-organize existing packs into a single, more efficient pack.
2016-01-29 22:53:50 +05:30
2019-07-31 22:56:46 +05:30
You can find this option under your project's **Settings > General > Advanced** .
2016-01-29 22:53:50 +05:30
