# Repair slower

You can make repair run slower by changing the level of parallelism or intensity.
By default ScyllaDB Manager runs repairs with full parallelism and intensity one.

Reduce amount of work performed by a single ScyllaDB repair job.
If `--intensity` has been previously increased, try setting it to `--intensity 1`. That reduces the number of token ranges repaired in a single ScyllaDB repair job.
Beware that 0 is a special value, it means max intensity.

Try setting `--parallel 1`, that would cap the number of ScyllaDB repair jobs in the cluster to one, frees nodes that are not being repaired.
This would have the same result as running ScyllaDB Manager 2.1 or earlier in terms of parallelism.

## Slowdown a running repair

If a repair is running on a cluster, you can change intensity and parallelism levels while it is running.
Run the following command to limit the number of parallel ScyllaDB repair jobs in the cluster to one.

```none
sctool repair control -c prod-cluster --parallel 1
```

You can view your current values for intensity and parallel with the [sctool progress](https://manager.docs.scylladb.com/branch-3.9/sctool/progress.md#task-progress) command.
Stopping the task and running again, would reset the values.

## Slowdown the future runs of a repair

If you wish to change intensity and parallelism level of a repair task use [sctool repair update](https://manager.docs.scylladb.com/branch-3.9/sctool/repair.md#repair-update) command.
Run the following command to limit the number of parallel ScyllaDB repair jobs in the cluster to one.

```none
sctool repair update -c prod-cluster repair/143d160f-e53c-4890-a9e7-149561376cfd --parallel 1
```