[SERVER-77661] Analyze why Storage Execution-related workloads have regressions with the potential TCMalloc upgrade Created: 31/May/23 Updated: 23/Jun/23 |
|
| Status: | Open |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Blake Oler | Assignee: | Backlog - Storage Execution Team |
| Resolution: | Unresolved | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Assigned Teams: |
Storage Execution
|
| Participants: |
| Description |
|
For each of the workloads linked in this document under the Storage Execution subheader indicated as "representative of the real world," come up with a paragraph explaining why the workload has regressed with the new TCMalloc (either THP on or off). If there is potential work that could improve this regression, please identify that. An index document is located here that has the analyses and links to specific runs. |