From a9c00d7d148e01b0f14c70d5e0ac18ccb773d6c3 Mon Sep 17 00:00:00 2001 From: Martin Mattel Date: Wed, 23 Oct 2024 17:10:17 +0200 Subject: [PATCH] [docs-only] Fix Antivirus readme --- services/antivirus/README.md | 6 +++++- 1 file changed, 5 insertions(+), 1 deletion(-) diff --git a/services/antivirus/README.md b/services/antivirus/README.md index caf7e99004..250cc071b1 100644 --- a/services/antivirus/README.md +++ b/services/antivirus/README.md @@ -18,6 +18,10 @@ Several factors can make it necessary to limit the maximum filesize the antiviru > [!CAUTION] > Streaming of files to the virus scan service still [needs to be implemented](https://github.com/owncloud/ocis/issues/6803). To prevent OOM errors `ANTIVIRUS_MAX_SCAN_SIZE` needs to be set lower than available ram. +### Antivirus Workers + +The number of concurrent scans can be increased by setting `ANTIVIRUS_WORKERS`. Be aware that this will also increase memory usage. + ### Infected File Handling The antivirus service allows three different ways of handling infected files. Those can be set via the `ANTIVIRUS_INFECTED_FILE_HANDLING` environment variable: @@ -44,4 +48,4 @@ The number of concurrent scans can be increased by setting `ANTIVIRUS_WORKERS`, ### Scaling in Kubernetes -In kubernetes `ANTIVIRUS_WORKERS` and `ANTIVIRUS_MAX_SCAN_SIZE` can be used to trigger the horizontal pod autoscaler by requesting a memory size that is below `ANTIVIRUS_MAX_SCAN_SIZE`. Keep in mind that `ANTIVIRUS_MAX_SCAN_SIZE` amount of memory might be held by `ANTIVIRUS_WORKERS` number of go routines. +In kubernetes, `ANTIVIRUS_WORKERS` and `ANTIVIRUS_MAX_SCAN_SIZE` can be used to trigger the horizontal pod autoscaler by requesting a memory size that is below `ANTIVIRUS_MAX_SCAN_SIZE`. Keep in mind that `ANTIVIRUS_MAX_SCAN_SIZE` amount of memory might be held by `ANTIVIRUS_WORKERS` number of go routines.