[SERVER-45596] Maximum number of clients supported by change stream Created: 16/Jan/20 Updated: 17/Jan/20 Resolved: 17/Jan/20 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Question | Priority: | Minor - P4 |
| Reporter: | Xikui Wang | Assignee: | Carl Champain (Inactive) |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||
| Participants: | |||||
| Description |
|
Hi Devs, I'm running some tests to figure out the maximum number of clients that can be supported by change stream. I basically took the script from I wonder probably the change stream is not designed for such use cases? What would be the maximum number of supportable clients in this case? Thank you! |
| Comments |
| Comment by Carl Champain (Inactive) [ 16/Jan/20 ] |
|
Hi xkkwww@gmail.com, The recommended maximum number of change stream cursors that a node can handle is 1000 (because of memory limitations and CPU workload), but we don't think even close to that is a reasonable target given how expensive some underlying mechanisms are. Importantly, your testing approach doesn’t work well, a general suggestion for how to do it better would be to use one stream per collection. For more details, I encourage you to ask our community by posting on the mongodb-user group or on Stack Overflow with the mongodb tag. Kind regards, |