[SERVER-37271] Perf test for bg index build and hybrid index build Created: 21/Sep/18 Updated: 29/Oct/23 Resolved: 27/Sep/18 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Storage |
| Affects Version/s: | None |
| Fix Version/s: | 4.1.4 |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Eric Milkie | Assignee: | Louis Williams |
| 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 NYC 2018-10-08 | ||||
| Participants: | |||||
| Description |
|
Write a test that measures the performance of a background index build on an otherwise idle server (no writes or reads occurring.) Compare this performance with the performance of the new hybrid index build. The hybrid index build should be no slower. This is because we expect the time taken to sort and bulk-load the index table should be faster than the time taken to write each individual index record without the bulk loader, at least for WiredTiger. For storage engines that do not support the bulk loader, the time taken might be slower. |