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

Add support for running multiple Tornado threads #372

Closed
timabbott opened this issue Dec 14, 2015 · 2 comments
Closed

Add support for running multiple Tornado threads #372

timabbott opened this issue Dec 14, 2015 · 2 comments
Labels
area: performance Performance and scalability issues help wanted priority: high

Comments

@timabbott
Copy link
Sponsor Member

As discussed in #54, one of the main scalability constraints for Zulip is the fact that its Tornado-based event system only supports a single Tornado process; eventually that process will get backlogged with traffic (probably around 5K active users, though one could stretch it considerably by changing the heartbeat frequency at the cost of having Zulip not work on networks that drop long-lived TCP connections).

I can post a branch with partial work towards this if anyone is interested in working on it...

@timabbott
Copy link
Sponsor Member Author

I finished implementing a basic version of this that supports using one Tornado process per realm, which is mostly merged into master (but doesn't yet have a supported way to configure it without a small fork).

@Gittenburg Gittenburg added area: performance Performance and scalability issues and removed area: production labels Jul 9, 2020
@timabbott
Copy link
Sponsor Member Author

Closing this ancient issue as we implemented Tornado sharding support and have been using it in production for some time.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area: performance Performance and scalability issues help wanted priority: high
Projects
None yet
Development

No branches or pull requests

2 participants