[SERVER-75661] Investigate 13% regression in insert_jfalse_wmajority Created: 04/Apr/23 Updated: 19/Apr/23 Resolved: 19/Apr/23 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Colby Ing | Assignee: | Backlog - Query Integration |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||
| Assigned Teams: |
Query Integration
|
||||||||||||
| Participants: | |||||||||||||
| Description |
|
Investigate or fix - when we turn the flag on in master, all > 10% regressions with z_scores > 2 will trigger automatic BF creation. This test failure has > 10% regression and >2.0 z_score.
|
| Comments |
| Comment by Charlie Swanson [ 19/Apr/23 ] |
|
This was investigated and spawned the linked tickets. The flame graphs showed those areas as pretty expensive. We think that insert is getting slower just because it is competing for resources with concurrent queries. We may have to look into this again after fixing the linked issues, but hope not to. |