[SERVER-67170] Avoid inspecting oplog BSON object for every insert request to change collection Created: 10/Jun/22 Updated: 06/Dec/22 Resolved: 13/Oct/22 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Rishab Joshi (Inactive) | Assignee: | Backlog - Query Execution |
| Resolution: | Won't Do | Votes: | 0 |
| Labels: | tech-debt | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Assigned Teams: |
Query Execution
|
| Participants: |
| Description |
|
The change collection code currently parses the BSON object to make various decisions. In the serverless, if the change collection mode is enabled, then every oplog entry will be inspected by the change collection. Examining every BSONified oplog entry might be expensive and could reduce the write performance. This ticket is about refactoring the change collection so we make such a decision by inspecting the oplogEntry IDL spec rather. It should be noted that at the time of filing this ticket, the change collection was in the development phase and no performance implications were known. This ticket is desirable but not mandatory. The priority of this ticket is also very low. |
| Comments |
| Comment by Githook User [ 13/Oct/22 ] |
|
Author: {'name': 'Rishab Joshi', 'email': 'rishab.joshi@mongodb.com', 'username': 'rishvin'}Message: |