From ac877bde815827f7aa1eeb3a6f0513d4c7503ad0 Mon Sep 17 00:00:00 2001 From: kim Date: Mon, 10 Nov 2025 12:36:59 +0100 Subject: [performance] add optional S3 object info caching (#4546) This adds an optional S3 object info cache to the S3 storage driver backend (see [here](https://codeberg.org/gruf/go-storage/releases/tag/v0.4.0)) to reduce S3 calls largely during media cleanup operations, but it should also help in other situations cutting back on S3 calls when for example a key is already known to not exist. Reviewed-on: https://codeberg.org/superseriousbusiness/gotosocial/pulls/4546 Co-authored-by: kim Co-committed-by: kim --- example/config.yaml | 11 +++++++++++ 1 file changed, 11 insertions(+) (limited to 'example') diff --git a/example/config.yaml b/example/config.yaml index bf6be2573..a7c679f38 100644 --- a/example/config.yaml +++ b/example/config.yaml @@ -288,6 +288,17 @@ cache: # Default: "100MiB" memory-target: "100MiB" + # cache.s3-object-info (if set) enables caching + # of S3 object information in the storage driver. + # This can help reduce S3 calls on metered buckets + # by caching simple information like whether an + # object exists, and if so, its size. Left unset, + # the cache will be disabled, which is the default. + # The given value determines the cache capacity. + # Examples: [0, 8000, 16000, 2560000] + # Default: 0 + s3-object-info: 0 + ###################### ##### WEB CONFIG ##### ###################### -- cgit v1.2.3