2020-06-23 00:09:42 +05:30
---
stage: Enablement
group: Geo
2021-02-22 17:27:13 +05:30
info: To determine the technical writer assigned to the Stage/Group associated with this page, see https://about.gitlab.com/handbook/engineering/ux/technical-writing/#assignments
2020-06-23 00:09:42 +05:30
type: howto
---
2021-03-11 19:13:27 +05:30
# Tuning Geo **(PREMIUM SELF)**
2019-07-31 22:56:46 +05:30
2020-10-24 23:57:45 +05:30
## Changing the sync/verification capacity values
2019-07-31 22:56:46 +05:30
2021-03-11 19:13:27 +05:30
In **Admin Area > Geo** (`/admin/geo/nodes`),
2020-04-08 14:13:33 +05:30
there are several variables that can be tuned to improve performance of Geo:
2019-07-31 22:56:46 +05:30
2020-10-24 23:57:45 +05:30
- Repository sync capacity
- File sync capacity
- Container repositories sync capacity
- Verification capacity
2019-07-31 22:56:46 +05:30
2020-10-24 23:57:45 +05:30
Increasing capacity values will increase the number of jobs that are scheduled.
2019-07-31 22:56:46 +05:30
However, this may not lead to more downloads in parallel unless the number of
available Sidekiq threads is also increased. For example, if repository sync
capacity is increased from 25 to 50, you may also want to increase the number
of Sidekiq threads from 25 to 50. See the
2019-09-04 21:01:54 +05:30
[Sidekiq concurrency documentation ](../../operations/extra_sidekiq_processes.md#number-of-threads )
2019-07-31 22:56:46 +05:30
for more details.
2020-10-24 23:57:45 +05:30
## Repository re-verification
See
[Automatic background verification ](../disaster_recovery/background_verification.md ).
