[SERVER-83249] Determine if sending each state record to the FileIO thread is becoming a bottleneck Created: 14/Nov/23 Updated: 28/Nov/23 Resolved: 28/Nov/23 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Mayuresh Kulkarni | Assignee: | Backlog - Atlas Streams |
| Resolution: | Won't Do | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||
| Assigned Teams: |
Atlas Streams
|
||||
| Participants: | |||||
| Description |
|
Today we send each operator provided state record to the FileIO thread (it is a move of a BSONObj). If we are dealing with a large number of small BSONObjs then this can become a bottleneck. We are expecting that this will not be the case - i.e. operators will do some internal batching on their own. If this assumption turns out to not be valid in practice, then we may have to revisit this issue. |
| Comments |
| Comment by Mayuresh Kulkarni [ 28/Nov/23 ] |
|
This issue is no longer needed and so can be closed |