From 41f49be8672987f49f4c75fbdc77331bfa0658bd Mon Sep 17 00:00:00 2001 From: Andrew Halberstadt Date: Tue, 16 Apr 2024 10:41:17 -0400 Subject: [PATCH] fix: set a more reasonable value for bitrisescript average_task_duration It's impossible to know the average task duration of these workers, because they entirely depend on how long the workflows take in Bitrise. It could be one minute or multiple hours. But 30 minutes seems like a reasonable middle ground. Also bump up the SLO value so we don't spin up new nodes as quickly. --- configs/relengworker-prod/config.yml | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/configs/relengworker-prod/config.yml b/configs/relengworker-prod/config.yml index 6d6205f..ad2bb55 100644 --- a/configs/relengworker-prod/config.yml +++ b/configs/relengworker-prod/config.yml @@ -317,8 +317,8 @@ worker_types: algorithm: slo args: max_replicas: 10 - avg_task_duration: 60 - slo_seconds: 120 + avg_task_duration: 1800 + slo_seconds: 600 capacity_ratio: 1.0 min_replicas: 0 @@ -331,8 +331,8 @@ worker_types: algorithm: slo args: max_replicas: 10 - avg_task_duration: 120 - slo_seconds: 240 + avg_task_duration: 1800 + slo_seconds: 300 capacity_ratio: 1.0 min_replicas: 0