paulmataruso/zulip
1
0
Fork 0
mirror of https://github.com/zulip/zulip.git synced 2025-11-02 13:03:29 +00:00
Code Issues Packages Projects Releases Wiki Activity

docs: Document Tornado sharding configurations.

Browse Source
This commit is contained in:
Alex Vandiver
2025-09-09 15:59:55 +00:00
committed by Tim Abbott
parent fa154b675d
commit 530685a597
3 changed files with 52 additions and 9 deletions
Download Patch File Download Diff File Expand all files Collapse all files

11
docs/subsystems/performance.md
View File

@@ -137,12 +137,11 @@ idle for a minute. It's likely that with some strategy for detecting
such situations, we could reduce their volume (and thus overall
Tornado load) dramatically.
Currently, Tornado is sharded by realm, which is sufficient for
arbitrary scaling of the number of organizations on a multi-tenant
system like zulip.com. With a somewhat straightforward set of work,
one could change this to sharding by `user_id` instead, which will
eventually be important for individual large organizations with many
thousands of concurrent users.
Currently, Tornado is sharded by realm, and optionally by user-id
within each realm. Sharding by realm is sufficient for arbitrary
scaling of the number of organizations on a multi-tenant system like
zulip.com. Sharding by user-id is necessary for very large
organizations with multiple thousands of active users at once.
### Presence