I have install airbyte via abctl local install, can anyone guide how to increase batch size and max_sync_jobs count

For

abctl local install

you’re running the standard Airbyte platform, so you tune concurrency via the same worker settings described in the docs. Increasing max concurrent sync jobs

MAX_SYNC_WORKERS

controls how many syncs a single worker can run in parallel. To raise the global concurrent sync limit you typically: 1. Increase

MAX_SYNC_WORKERS

. 2. (Optionally) increase the number of worker replicas if you’re on Kubernetes. 3. Ensure your infrastructure has enough CPU/memory for the extra connector pods. In Helm-style configuration this is done via:

worker:
  maxSyncWorkers: 10        # or higher, e.g. 20
  maxCheckWorkers: 10       # usually keep in sync with maxSyncWorkers
  replicaCount: 2           # number of worker pods

On older/“V1” style charts or env-based config it’s:

worker:
  extraEnv:
    - name: MAX_SYNC_WORKERS
      value: "10"
    - name: MAX_CHECK_WORKERS
      value: "10"

These variables directly cap concurrent syncs per worker. [Scaling Airbyte; Worker config] After changing these values, restart/redeploy Airbyte so the new env vars take effect. Increasing “batch size” The provided knowledge sources do not describe a generic “batch size” setting at the platform level (e.g., rows per batch) and do not show how to change it via

abctl

. I’m sorry, but there’s no information in these docs about a global batch-size knob; batch behavior is usually connector-specific and not covered in the snippets you shared. If you can clarify which connector you’re using and what you mean by “batch size” (e.g., number of records per page, per write batch, etc.), I can check if there’s connector-specific configuration in other docs. 👍 0 button 👎 0 button ℹ️ Tip: Mention @kapa.ai in the thread for follow-ups or DM the app for 1-to-1 help.