BREAKING server: disable deliver rate limit by default
ci/woodpecker/push/lint-client Pipeline was successful Details
ci/woodpecker/push/lint-backend Pipeline was successful Details
ci/woodpecker/push/build Pipeline was successful Details
ci/woodpecker/push/lint-foundkey-js Pipeline was successful Details
ci/woodpecker/push/lint-sw Pipeline was successful Details
ci/woodpecker/push/test Pipeline was successful Details

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 #190

Changelog: Changed
This commit is contained in:
Johann150 2023-02-04 17:57:52 +01:00
parent 9a6bb8be7d
commit 41c42f96f0
Signed by: Johann150
GPG Key ID: 9EE6577A2A06F8F1
2 changed files with 2 additions and 2 deletions

View File

@ -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.

View File

@ -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,