[SERVER-38431] Improve BSON validation performance Created: 05/Dec/18 Updated: 06/Dec/22 Resolved: 19/Apr/19 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Performance |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Tess Avitabile (Inactive) | Assignee: | Backlog - Service Architecture |
| Resolution: | Won't Fix | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||
| Assigned Teams: |
Service Arch
|
||||
| Sprint: | Service Arch 2019-03-25, Service Arch 2019-04-08, Service Arch 2019-04-22 | ||||
| Participants: | |||||
| Description |
|
In a performance investigation of initial sync, we found that for certain workloads, there is a bottleneck in performing BSON validation. By turning off validation on the source and target, initial sync time was reduced by up to 18%. The greatest savings occurred with large documents (since the bottleneck for small documents is insertion on the target) and documents containing nested arrays (since BSON validation was slower in this case). We should investigate if there is any low-hanging fruit in improving performance of BSON validation. |
| Comments |
| Comment by Mira Carey [ 19/Apr/19 ] |
|
Closing ithis out with the understanding that there is no obvious low hanging fruit available in bson validation performance |
| Comment by Mira Carey [ 11/Mar/19 ] |
|
redbeard0531, Feel free to close this out if there isn't any low hanging fruit you can think of |