microsoft / microsoft/multilspy
The request_definition function takes much time to return result
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 610
- Forks
- 111
- PR merge metrics
- No merged PRs in 30d
Description
I’m using this library to retrieve definitions of code elements for Java. The request_definition function is one I use frequently. However, I’ve noticed that the first request takes about 10 to 30 seconds to complete, and in some cases, it can take as long as 100 seconds. Subsequent requests are faster, taking around 5 to 10 seconds, but this still feels excessive. I’m not sure if this behavior is normal, but it’s too slow for my needs.
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 request_definition for both the first and subsequent requests, then inspect how it communicates with the Java language server. Compare the observed timings with the reported 10–30 second initial calls, occasional 100-second calls, and 5–10 second later calls; done means identifying the source of the delay and documenting or fixing it.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java, python
- Domain
- performance, tooling
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100