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
2021-09-04 01:27:46 +05:30
You can limit the number of concurrent operations the nodes can run
in the background.
2019-07-31 22:56:46 +05:30
2021-09-04 01:27:46 +05:30
## Changing the sync/verification concurrency values
2019-07-31 22:56:46 +05:30
2021-09-04 01:27:46 +05:30
On the **primary** site:
2019-07-31 22:56:46 +05:30
2021-11-11 11:23:49 +05:30
1. On the top bar, select **Menu > Admin** .
2021-09-04 01:27:46 +05:30
1. On the left sidebar, select **Geo > Nodes** .
1. Select **Edit** of the secondary node you want to tune.
1. Under **Tuning settings** , there are several variables that can be tuned to
improve the performance of Geo:
- Repository synchronization concurrency limit
- File synchronization concurrency limit
- Container repositories synchronization concurrency limit
- Verification concurrency limit
Increasing the concurrency 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
2021-09-04 01:27:46 +05:30
available Sidekiq threads is also increased. For example, if repository synchronization
concurrency is increased from 25 to 50, you may also want to increase the number
2019-07-31 22:56:46 +05:30
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 ).
