redhat-developer / redhat-developer/lsp4ij
Cache mapping between file and servers
Open
Nobody has claimed this yet.
performance
- Dominant language
- Java
- Stars
- 344
- Forks
- 113
- Avg merge
- 5h 22m
- Merged PRs (30d)
- 15
Description
Today on each LSP operations, mapping (which uses DocumentMatcher) are processed, it could be better to cache them to have better performance (if we see that performance is degraded).
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
Start by tracing the LSP operations that process mappings through DocumentMatcher and measure their current performance. Determine the cache scope and invalidation requirements, then verify that repeated mappings are faster without using outdated file-to-server results.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- performance, tooling
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100