[SERVER-70325] POC: Investigate cost of tracking memory allocations Created: 07/Oct/22 Updated: 29/Aug/23 Resolved: 29/Aug/23 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Louis Williams | Assignee: | Backlog - Service Architecture |
| Resolution: | Duplicate | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Assigned Teams: |
Service Arch
|
||||||||
| Participants: | |||||||||
| Description |
|
Write a POC to track per-operation memory utilization. We will do something similar to what the heap profiler is already doing. The plan is to intercept malloc and free calls to track memory usage per-Client (thread local). We are interested only in knowing the overhead of such a mechanism on our existing performance workloads. It should be able to sample to approximate memory usage with some loss of precision. |
| Comments |
| Comment by Phoebe Du [ 29/Aug/23 ] |
|
We will address this ticket in PM-3480. |