Implement separate connection limits per user #69
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Implements separate connection limits per user, to avoid scenarios where high traffic for a particular user can exhaust the connection pool and cause issues for other users.
This is configured by a new option
homeserver.connection_limit_per_user
(defaults to10
).It can be used alongside
homeserver.connection_limit
(from #64) which still applies to the appservice itself.Example addition to a config file: