You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Generally the language server should work well within the resource constraints of the machine that it is running on. i.e. it shouldn't use excessive amount of CPU.
The most common way of achieving this in Go is to cap number of concurrent operations to the number of available CPUs, i.e. runtime.NumCPU().
This should provide balance (between speed and CPU usage) for most users, but in some cases the user may wish to trade speed for CPU or vice versa - for example when they're actually more constrained and multiple other processes are competing for the same CPUs.
Proposal
Introduce -req-concurrency flag to terraform-ls serve which will control the concurrency of the underlying jrpc2 library. That way users have an escape hatch they can utilize in described (hopefully rare) cases.
The text was updated successfully, but these errors were encountered:
I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues.
If you have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.
Current Version
Use-cases
Generally the language server should work well within the resource constraints of the machine that it is running on. i.e. it shouldn't use excessive amount of CPU.
The most common way of achieving this in Go is to cap number of concurrent operations to the number of available CPUs, i.e.
runtime.NumCPU()
.This should provide balance (between speed and CPU usage) for most users, but in some cases the user may wish to trade speed for CPU or vice versa - for example when they're actually more constrained and multiple other processes are competing for the same CPUs.
Proposal
Introduce
-req-concurrency
flag toterraform-ls serve
which will control the concurrency of the underlying jrpc2 library. That way users have an escape hatch they can utilize in described (hopefully rare) cases.The text was updated successfully, but these errors were encountered: