Motivation
Steps to repro:
- Open kimchi and do some work in a go project
- Leave for lunch
- Come back
- Observe that gopls is spawned, running and consuming resources
On large codebases, gopls can easily consume 1-3 GiB RAM even when doing nothing right now, just to keep state active. Now imagine 10 kimchi sessions waiting for a button press.
Proposed solution
Stop gopls after some idle time (let's say 10-15 minutes) so it is "hot" while user is active but does not consume resources from a forgotten kimchi session 3 days ago.
If this works well, the same idea can be implemented for other background processes.
Alternatives considered
No response
Motivation
Steps to repro:
On large codebases, gopls can easily consume 1-3 GiB RAM even when doing nothing right now, just to keep state active. Now imagine 10 kimchi sessions waiting for a button press.
Proposed solution
Stop gopls after some idle time (let's say 10-15 minutes) so it is "hot" while user is active but does not consume resources from a forgotten kimchi session 3 days ago.
If this works well, the same idea can be implemented for other background processes.
Alternatives considered
No response