Skip to content
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

Avoid multiple serialize-deserialize cycles when returning results to Language Server clients #5741

Closed
hubertp opened this issue Feb 22, 2023 · 1 comment
Assignees
Labels
--low-performance -compiler p-low Low priority s-research-needed Status: the task will require heavy research to complete

Comments

@hubertp
Copy link
Collaborator

hubertp commented Feb 22, 2023

Every time Language Server returns a value reported by runtime we go through serialize-deserialize conversion.
Currently, this is necessary because runner and runtime jars are not loaded using the same classloader.

A proposal was made in #5419 to switch to in-memory protocol but that might involve a rather deep rewrite of Language Server.
This ticket proposes to consider introducing data structures that can be shared between the two process without the costly serialization.
We have to investigate if there is a way to workaround the classloader issue.

@JaroslavTulach JaroslavTulach closed this as not planned Won't fix, can't repro, duplicate, stale Jan 9, 2025
@github-project-automation github-project-automation bot moved this from ❓New to 🟢 Accepted in Issues Board Jan 9, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
--low-performance -compiler p-low Low priority s-research-needed Status: the task will require heavy research to complete
Projects
Status: 🟢 Accepted
Development

No branches or pull requests

3 participants