limited both scheduler to 1 CPU fix

.env.example

@@ -223,9 +223,6 @@ TOMCAT_PROXY_URL=${PROXY_URL}/sta/
 SCHEDULER_IMAGE_TAG=latest
 # This is used in the Dockerfile of basic-demo-scheduler
 EXTRACTOR_IMAGE_TAG=latest
-# Adjust to your local machine [max: CPUS-1]
-SCHEDULER_CPU_COUNT=2
-
 
 ############################################################
 # cron-scheduler (debian, python)

docker-compose.yml

@@ -743,9 +743,9 @@ services:
   basic-demo-scheduler:
     image: "registry.hzdr.de/ufz-tsm/tsm-basic-demo-scheduler/basic_demo_scheduler:${SCHEDULER_IMAGE_TAG}"
     restart: "${RESTART}"
-    # prevent blocking/slowing-down of other services
-    # if many scheduler jobs occur at the same time
-    cpu_count: ${SCHEDULER_CPU_COUNT}
+    # Prevent blocking/slowing-down of other services if many scheduler jobs occur at
+    # the same time. Cap the processing power to equivalent of one CPU of the system.
+    cpus: 1.0
     healthcheck:
       test: [ "CMD-SHELL", "curl --fail http://localhost:5000/health || exit 1" ]
       interval: 10s
@@ -768,6 +768,9 @@ services:
         UID: "${UID}"
         DEBIAN_IMAGE_TAG: "${CRON_DEBIAN_IMAGE_TAG}"
     restart: "${RESTART}"
+    # Prevent blocking/slowing-down of other services if many scheduler jobs occur at
+    # the same time. Cap the processing power to equivalent of one CPU of the system.
+    cpus: 1.0
     environment:
       SETUP_SERVICE: "${CRON_SETUP_SERVICE}"
       CREATEDB_POSTGRES_USER: "${CRON_CREATEDB_POSTGRES_USER}"