Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Implement separate connection limits per user #69

Conversation

justinbot
Copy link
Contributor

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 to 10).
It can be used alongside homeserver.connection_limit (from #64) which still applies to the appservice itself.

Example addition to a config file:

homeserver:
    ...
    # Maximum number of simultaneous HTTP connections to the homeserver for a particular user.
    connection_limit_per_user: 5

@tulir
Copy link
Member

tulir commented Nov 18, 2021

This looks like a per-ghost connection limit, which I think in practice means there's just no limit? (because the bridge probably won't do that much stuff simultaneously with a single ghost user)

@justinbot justinbot closed this Nov 29, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

Successfully merging this pull request may close these issues.

2 participants