A Neovim plugin that automatically stops idle LSP servers and restarts them on focus to reduce RAM usage.
lsp-timeout.nvim is a Neovim plugin that automatically manages Language Server Protocol (LSP) server lifecycles to optimize memory usage. It stops idle LSP servers and restarts them when needed, such as upon regaining window focus, preventing excessive RAM consumption and keeping Neovim responsive.
Neovim users who utilize nvim-lspconfig and work with memory-inefficient LSP servers that can consume gigabytes of RAM if left running. It is particularly valuable for developers on systems with limited memory or those who keep Neovim open for extended periods.
Developers choose this plugin to automatically mitigate memory bloat from poorly optimized LSP servers, ensuring Neovim remains fast without manual intervention. Its unique selling point is the automatic stop-and-restart mechanism triggered by window focus events, which directly targets a common pain point in LSP setups.
Automatically start/stop LSP servers, keeps RAM usage low
Open-Awesome is built by the community, for the community. Submit a project, suggest an awesome list, or help improve the catalog on GitHub.
Stops idle LSP servers upon losing window focus, directly addressing memory bloat from inefficient servers as highlighted in the README's focus on preventing gigabytes of RAM usage.
Restarts servers automatically when regaining window focus, ensuring LSP functionality resumes without manual intervention, which is core to its automated lifecycle management.
Works specifically with nvim-lspconfig, a standard Neovim plugin, making setup straightforward for users already leveraging this common configuration.
Prioritizes keeping Neovim fast by unloading unused servers, aligning with its philosophy of resource efficiency for long coding sessions.
The README explicitly states 'NO GUARANTEES UNTIL PAID,' indicating potential instability or lack of support for unpaid users in critical environments.
Relies solely on window focus events for stop/start triggers, which may not handle all inactivity scenarios and can be problematic in multi-window or headless workflows.
Lacks detailed configuration options in the provided README; users must dig into linked documentation for advanced tuning, suggesting a sparse out-of-box experience.
Frequent server restarts on focus changes can cause perceptible delays, especially for LSP servers that are slow to initialize, impacting developer flow.