From 4a6cb82c44a5d7e44a945f00a18926c0bc91a378 Mon Sep 17 00:00:00 2001 From: Alex Chapellon Date: Thu, 6 Jun 2024 14:46:29 +0200 Subject: [PATCH] Apply suggestions from code review Co-authored-by: Giovanni Toraldo <71768+gionn@users.noreply.github.com> --- docs/helm/autoscaling.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/docs/helm/autoscaling.md b/docs/helm/autoscaling.md index bf9fe67c9..5529fe25b 100644 --- a/docs/helm/autoscaling.md +++ b/docs/helm/autoscaling.md @@ -97,7 +97,7 @@ alfresco-repository: ##### Prometheus scaler -The KEDA based auto scaler relies on the number of Tomcat thread used. By +The KEDA based auto scaler relies on the number of Tomcat threads used. By default the Alfresco repository image uses up to 200 threads. When the system consistently uses more than 170 threads, the KEDA scaler will start to scale up the number of pods. This can be tuned using the @@ -166,7 +166,7 @@ T-engine workloads (`imagemagick`, `libreoffice`, `transformmisc`, `pdfrenderer` > `pdfrenderer` & `tika`. Scaling replicas down to zero is great when you have workload that is consistent -enough with long period of inactivity (e.g. overnigh). But it can trigger a +enough with long period of inactivity (e.g. during the night). But it can trigger a delay for the first requests when the workload starts again (e.g. the morning after). If you want to avoid scaling down you ATS deployments down to zero and always have at least one pod up to deal quickly with "sparse" requests just @@ -184,7 +184,7 @@ alfresco-transform-service: need to set the `kedaIdleReplicas` to `0` for all tengines, otherwise the T-router will eventually crash. -If you want to use an external ActiveMQ broker instead of the embeded one +If you want to use an external ActiveMQ broker instead of the embedded one (recommended), you can set the following values: ```yaml