-
Notifications
You must be signed in to change notification settings - Fork 35
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Pull diagonostics #49
Comments
What are the general performance issues? |
Having lots of diagnostics around is generally quite slow for vscode. You are the original author of the performance issues comment however here. :-) |
I was asking because there are a few different concerns w.r.t. performance. Pull diagnostics solve quite a few other general performance issues related to diagnostics, and I think indeed it does help vscode too. @corwin-of-amber , @Alizter , actually it is a pity that https://microsoft.github.io/language-server-protocol/specifications/lsp/3.17/specification/#textDocument_diagnostic doesn't include a document point in the request, that would actually be almost enough as to have an idea of what the viewport is, and only check that part of the document. Maybe we should open an issue upstream? I've commented on microsoft/language-server-protocol#737 |
To give an idea of what
take them with a grain of salt, as all informal timings, but that seems significative. |
I was trying to understand how partial Pull Diagnostics work, but I couldn't really figure out from the spec :/ |
Diagnostics should be pulled on demand rather than all given at once.
Unlikely to solve general performance issues around them however.
Problems with current setup:
ok_diagnostics
The text was updated successfully, but these errors were encountered: