[SERVER-32755] Expand Evergreen microbenchmark coverage for unique index format change Created: 18/Jan/18 Updated: 30/Oct/23 Resolved: 05/Mar/18 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Storage |
| Affects Version/s: | None |
| Fix Version/s: | 3.7.3 |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Neha Khatri | Assignee: | Sulabh Mahajan |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||
| Sprint: | Storage 2018-02-26, Storage Non-NYC 2018-03-12 | ||||||||
| Participants: | |||||||||
| Description |
|
Unique Index format is going to change as part of the work planned for this epic. It would be useful to expand Evergreen microbenchmark tests to cover unique index better. Currently there is query benchmark that uses unique indexes. We should add cases to insert and update benchmark that similarly use unique indexes. |
| Comments |
| Comment by Githook User [ 16/Mar/18 ] |
|
Author: {'email': 'sulabh.mahajan@mongodb.com', 'name': 'Sulabh Mahajan', 'username': 'sulabhM'}Message: |
| Comment by Githook User [ 05/Mar/18 ] |
|
Author: {'email': 'sulabh.mahajan@mongodb.com', 'name': 'Sulabh Mahajan', 'username': 'sulabhM'}Message: |