Feature: Unmutable in-memory indexes for Active fraction
Open
Nobody has claimed this yet.
feature
- Dominant language
- Go
- Stars
- 131
- Forks
- 16
- Avg merge
- 2d 4h
- Merged PRs (30d)
- 11
Description
- Optimize performance index structure getting rid of concurrent writing
- Optimize index structure for performant search (sort tokens and ids)
- Optimize index structure for merging several indexes into one
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
No files, tests, or entry points are named. Begin by locating the in-memory index implementation and its search and merge tests, then determine how concurrent writes are currently handled. Done should cover immutable indexes, sorted tokens and IDs for search, and merging several indexes into one without concurrent writing.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- databases, performance, search
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100