From 41c42f96f0464ead2ef1bfb862be6085dd2fa340 Mon Sep 17 00:00:00 2001 From: Johann150 Date: Sat, 4 Feb 2023 17:57:52 +0100 Subject: [PATCH] BREAKING server: disable deliver rate limit by default The deliver rate limit seems to cause a lot of performance problems, presumably because of the overhead the rate limit has. It also does not really make sense to rate limit outgoing because we are requesting from different servers anyway. fixes https://akkoma.dev/FoundKeyGang/FoundKey/issues/190 Changelog: Changed --- .config/example.yml | 2 +- packages/backend/src/config/load.ts | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/.config/example.yml b/.config/example.yml index 0cf399a64..4146881b1 100644 --- a/.config/example.yml +++ b/.config/example.yml @@ -100,7 +100,7 @@ redis: # Use -1 to disable. # A rate limit for deliver jobs is not recommended as it comes with # a big performance penalty due to overhead of rate limiting. -#deliverJobPerSec: 128 +#deliverJobPerSec: -1 #inboxJobPerSec: 16 # Number of times each job will be tried. diff --git a/packages/backend/src/config/load.ts b/packages/backend/src/config/load.ts index 9adf5677b..133a6f4ff 100644 --- a/packages/backend/src/config/load.ts +++ b/packages/backend/src/config/load.ts @@ -54,7 +54,7 @@ export default function load(): Config { disableHsts: false, deliverJobConcurrency: 128, inboxJobConcurrency: 16, - deliverJobPerSec: 128, + deliverJobPerSec: -1, inboxJobPerSec: 16, deliverJobMaxAttempts: 12, inboxJobMaxAttempts: 8,