From 16982c307f4718c5de0190525d8a280d2cbeb7d8 Mon Sep 17 00:00:00 2001 From: Kliachin Aleksei Date: Wed, 4 Feb 2026 13:04:48 +0800 Subject: [PATCH] Allow configuring Sentry taskworker concurrency via env (#4149) * Allow configuring Sentry taskworker concurrency via env * Update comment for SENTRY_TASKWORKER_CONCURRENCY ENV --- .env | 2 ++ docker-compose.yml | 2 +- 2 files changed, 3 insertions(+), 1 deletion(-) diff --git a/.env b/.env index d75f181..4988930 100644 --- a/.env +++ b/.env @@ -9,6 +9,8 @@ SENTRY_EVENT_RETENTION_DAYS=90 SENTRY_BIND=9000 # Set SENTRY_MAIL_HOST to a valid FQDN (host/domain name) to be able to send emails! # SENTRY_MAIL_HOST=example.com +# Parallel taskworker processes (higher values increase memory usage; >32 not recommended) +SENTRY_TASKWORKER_CONCURRENCY=4 SENTRY_IMAGE=ghcr.io/getsentry/sentry:nightly SNUBA_IMAGE=ghcr.io/getsentry/snuba:nightly RELAY_IMAGE=ghcr.io/getsentry/relay:nightly diff --git a/docker-compose.yml b/docker-compose.yml index c8a5c2b..13db0c5 100644 --- a/docker-compose.yml +++ b/docker-compose.yml @@ -745,7 +745,7 @@ services: command: run taskworker-scheduler taskworker: <<: *sentry_defaults - command: run taskworker --concurrency=4 --rpc-host=taskbroker:50051 --health-check-file-path=/tmp/health.txt + command: run taskworker --concurrency=$SENTRY_TASKWORKER_CONCURRENCY --rpc-host=taskbroker:50051 --health-check-file-path=/tmp/health.txt healthcheck: <<: *file_healthcheck_defaults vroom: