Memory Leaks during batch point inserts
Open
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 464
- Forks
- 46
- PR merge metrics
- No merged PRs in 30d
Description
Hello
I'm using the library using the REST client to batch insert points (by 1000) in a cloud QDrant cluster.
After 185000 points inserted my script crashed, running out of heap. (the node process was using 4GB of memory at that time)
I can not deep dive into the issue, but I was able to perform my task using the REST API directly.
Regards
Contributor guide
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
The issue names no file or test entry point. Start by reproducing batch inserts of 1,000 points through the TypeScript REST client and compare memory usage with direct REST calls. Done means the client can insert beyond 185,000 points without exhausting the Node.js heap.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- api, databases
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100