Memory tracker for mvmap
Open
sig/execution
type/enhancement
- Dominant language
- Go
- Stars
- 40.5k
- Forks
- 6.2k
- PR merge metrics
- PR metrics pending
Description
## Enhancement
There is an amount of memory occupied by mvmap, but it seems that it can't be tracked by the memory tracker.
Contributor guide
Research direction
Locate the mvmap implementation and the memory tracker entry points, then read how mvmap memory is currently allocated and reported. The work is complete when the memory occupied by mvmap is included in the memory tracker’s accounting.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- backend, databases
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100