> For the complete documentation index, see [llms.txt](https://docs.collibra.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.collibra.com/data-quality-self-hosted/admin-configuration/more-admin-settings/job-management/concurrency/overriding-the-default-batch-size.md).

# Overriding the default batch size

Unless you set the batch size in the owl-env.sh script for Standalone deployments or the Helm chart for Cloud native deployments, the batch size defaults to 5. This means that the DQ Agent applies a limit of 5 Jobs that can run concurrently. This page shows you how to override the default batch size for both Standalone and Cloud native deployments.

{% tabs %}
{% tab title="Standalone" %}
{% stepper %}
{% step %}
Open a terminal session.
{% endstep %}

{% step %}
Open the owl-env.sh file with the following command:

```
vi /home/owldq/owl/config/owl-env.sh
```

{% endstep %}

{% step %}
Use a base64 encoder, such as the free encoder from [base64encode.org](https://www.base64encode.org/), to encode the string `default?batchSize=5` (replacing `5` with your desired value) and enter the encoded value after `DEFAULT_BATCH_ID` in the following command:

```
# The string "default?batchSize=5" needs to be base64 encoded
export DEFAULT_BATCH_ID=default?batchSize=5
```

<i class="fa-glasses-round">:glasses-round:</i> Example: Your base64 encoded value should resemble the following example:`export DEFAULT_BATCH_ID=ZGVmYXVsdD9iYXRjaFNpemU9NQ==`

***

{% endstep %}

{% step %}
Enter the following command:

```
export DEFAULT_BATCH_SIZE=<your-batch-size>  
```

{% hint style="success" %}
The value in `<your-batch-size>` should meet the [concurrency sizing](/data-quality-self-hosted/admin-configuration/more-admin-settings/job-management/concurrency/concurrency-sizing.md) requirements of your use case.
{% endhint %}
{% endstep %}

{% step %}
End the terminal session.
{% endstep %}
{% endstepper %}
{% endtab %}

{% tab title="Cloud native" %}
{% stepper %}
{% step %}
Open a terminal session.
{% endstep %}

{% step %}
Enter the following command to pass your new default values to your agent batch ID and agent batch size:

```
--set global.configMap.data.agent_batch_id="default?batchSize=<your-batch-size>" 
--set global.configMap.data.agent_batch_size="<your-batch-size>"
```

{% hint style="success" %}
Enter a value in `<your-batch-size>` that meets the [concurrency sizing](/data-quality-self-hosted/admin-configuration/more-admin-settings/job-management/concurrency/concurrency-sizing.md) requirements for your use case.
{% endhint %}

1. If your Collibra DQ app is managed by an alternative Kubernetes package manager, ensure you update the **owl-agent-configmap** with the following variables:

   ```
   AGENT_BATCH_ID: "your-base64-encoded-value"
   AGENT_BATCH_SIZE: \<your-batch-size\>
   ```

   <i class="fa-glasses-round">:glasses-round:</i> Example: Your base64 encoded string should resemble the following example:`export AGENT_BATCH_ID=QUdFbVlYWnNkRDRpWVpiZXZGTnBlbVU5Tkw9PQ==`

   <div data-gb-custom-block data-tag="hint" data-style="success" class="hint hint-success"><p>Enter a value in <code>&#x3C;your-batch-size></code> that meets the <a href="/data-quality-self-hosted/admin-configuration/more-admin-settings/job-management/concurrency/concurrency-sizing.md">concurrency sizing</a> requirements for your use case.</p></div>
2. Restart the DQ agent pod to complete the updates.
   {% endstep %}

{% step %}
Choose one of the following options to update your DQ agent resources:

1. Update the DQ agent from the user interface
   1. Sign in to Collibra DQ.
   2. Hover your cursor over the <img src="https://4121921244-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FWCrP7Albs8DfJjIQxUxw%2Fuploads%2Fgit-blob-75245abf5c50ddf56f1d2d727ccaacf757d11145%2Fcogwheel-large%402x.png?alt=media" alt="" data-size="line"> icon and click **Admin Console**.\ <i class="fa-chevrons-right">:chevrons-right:</i> The Admin Console opens.
   3. Click **Remote Agent**.\ <i class="fa-chevrons-right">:chevrons-right:</i> The **Agent Management** page opens.
   4. Click the pencil icon.\ <i class="fa-chevrons-right">:chevrons-right:</i> The **Edit Agent** modal opens.
   5. Update **Number of Executors**, **Executor Memory**, **Number of Cores**, and **Driver Memory** according to the [concurrency sizing](/data-quality-self-hosted/admin-configuration/more-admin-settings/job-management/concurrency/concurrency-sizing.md) requirements for your use case.
   6. Click **Save**.
2. Update the DQ agent through Helm to set your new limits
   1. Open a terminal session.
   2. In your Helm values.yaml file, update the DQ agent's `memory` and `cpu` quotas according to the [concurrency sizing](/data-quality-self-hosted/admin-configuration/more-admin-settings/job-management/concurrency/concurrency-sizing.md) requirements for your use case:

      ```
      global:
                                          agent:
                                          enabled: true
                                          replicaCount: 1
                                          nodeSelector:
                                          key: ""
                                          value: ""
                                          resources:
                                          requests:
                                          memory: "\<your-new-memory-value\>"
                                          cpu: "\<your-new-cpu-value\>"
                                          limits:
                                          memory: "\<your-new-memory-value\>"
                  cpu: "\<your-new-cpu-value\>"
      ```
   3. Perform the Helm upgrade on the existing DQ release.
   4. End the terminal session.
      {% endstep %}
      {% endstepper %}
      {% endtab %}
      {% endtabs %}