C API: IodeContents too slow for large KDB
Open
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 2
- Forks
- 1
- Avg merge
- 7h 35m
- Merged PRs (30d)
- 13
Description
Rewrite IodeContents() with regex or a better algorithm because K_grep() is VERY slow for large databases.
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 at the C API entry point IodeContents() and inspect how it calls K_grep(). Profile both paths on a large KDB, then compare the rewritten implementation against the current results while confirming that lookup behavior is preserved and runtime improves.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- api, performance
- Issue type
- Refactor
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100