[SERVER-57296] Consider adding a perf test for logical session refresh Created: 28/May/21 Updated: 12/Dec/23 |
|
| Status: | Backlog |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Janna Golden | Assignee: | Backlog - Cluster Scalability |
| Resolution: | Unresolved | Votes: | 0 |
| Labels: | sharding-nyc-subteam2, sharding-wfbf-day | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Assigned Teams: |
Cluster Scalability
|
| Participants: | |
| Story Points: | 5 |
| Description |
|
In HELP-24525, the Atlas profiler was marking updates to the systems collection as slow and the user wanted to confirm whether the durations seen were expected, but we don't currently have a performance test for the logical session cache refresh to get a baseline. The default refresh period is 5 minutes, and if a user creates a lot (1000s let's say) sessions in that time period then we'll be doing multiple writes to the sessions collection with batch sizes of 1000. It might be useful to get baseline numbers for how long we expect the refresh to take for a large number of sessions. |