raw client batch put memory leak
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 425
- Forks
- 163
- Avg merge
- 10h 51m
- Merged PRs (30d)
- 3
Description
valgrindbak.log this is my db bench valgrind analyze result. i need put 10 million custom record data to tikv for query loadtest.
And I've identified a memory leak issue in the client application. As the data volume increases, the memory usage grows progressively. When inserting 10 million records, the memory consumption reaches 700MB, which is unreasonable given that:
My concurrency is strictly limited to 100,000 operations and I only have about 60 bytes per record
The memory usage accumulates gradually over time
This linear growth pattern suggests unmanaged resource retention
:=/
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.
Research direction
Start with the attached valgrindbak.log and reproduce the reported raw client batch put workload using 10 million custom records and the stated concurrency. Compare memory usage as records are inserted and identify the retained resources; done means the client no longer shows the reported progressive growth toward 700MB.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- databases
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100