MemoryTracker accuracy test detected large untracked memory usage
@yibin87 is already working on this.
Since Mar 7, 2025.
- Dominant language
- C++
- Stars
- 1k
- Forks
- 423
- Avg merge
- 1d 15h
- Merged PRs (30d)
- 24
Description
Our tcms test MemoryTrackerAccuracy runs 100 concurrency tpch-1 test, to check if RSS(Resident Set Size) > TrackedMaxMemory + 3.4G, it failed now. Confirmed that adjust 3.4G=>5G, the test can pass.
The increased untracked memory usage may have been introduced for a long time. However, our test framework accidentally treats error msg with "exceeds" keywork as context done, thus the real test only runs for about 10 minutes which is much smaller than the expected 1 hour.
Recently, we fixed the test framework issue, and exposed the untracked memory usage increase issue.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Assessment
This issue has not been assessed yet.