getappmap / getappmap/appmap-js
Fix performance with large repositories
Open
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 53
- Forks
- 18
- Avg merge
- 3d 18h
- Merged PRs (30d)
- 8
Description
With large repositories, performance can be abysmal, in several areas:
- context search,
- indexing,
- uptodate.
Perhaps we can even remove the last one (at least for now), we're barely using that and the performance impact on interactive usage can be really significant.
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 by profiling the context search, indexing, and uptodate paths on large repositories to identify where interactive performance degrades. Determine whether uptodate can be removed or reduced, then define measurable performance targets and verify them against representative large repositories.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- performance, search
- Issue type
- Bug
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100