You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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...
The text was updated successfully, but these errors were encountered:
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).
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...
The text was updated successfully, but these errors were encountered: