nvim-lua/completion-nvim

Performance issues with large codebases

Open

#203 opened on Sep 11, 2020

View on GitHub
 (46 comments) (0 reactions) (0 assignees)Lua (77 forks)batch import
help wantedimportant

Repository metrics

Stars
 (995 stars)
PR merge metrics
 (No merged PRs in 30d)

Description

I'm facing massive performance issues with a project that I'm working on which contains a lot of files. In this codebase completion is nearly unusable, causes lots of Lua & out of memory errors & crashes the native LSP.

One of the very common errors I get is this

Error executing luv callback:
...ovim/HEAD-7ba28b1/share/nvim/runtime/lua/vim/lsp/rpc.lua:558: cannot resume dead coroutine
Press ENTER or type command to continue

To make sure this was not the native LSP itself, I did the following:

  • Removed all the plugins
  • Installed all of them including nvim-lspconfig but without completion-nvim
  • Tested (with omni-completion setlocal omnifunc=v:lua.vim.lsp.omnifunc) -> everything ran very smoothly & fast
  • Installed completion-nvim
  • Tested -> performance issues all over the place (editor is locked, completion takes a lot of time, etc…)

I tried to see if coc.nvim has the same issues or no & I tried that & it worked fine too.

This is my completion.nvim config & this is my LSP config

Note, the same exact LSP config works fine without completion.nvim which also means that the TypeScript LSP is not the culprit too.

Contributor guide

Research direction
Start by profiling completion nvim's async handling with large codebases, focusing on how the plugin processes LSP completion responses. Compare with coc.nvim's implementation to identify potential bottlenecks. Examine the source code in the repository (e.g., the main completion loop and trigger handlers) and test with a large TypeScript project to reproduce the issue. Consider checking existing comments for any identified root causes or suggested fixes.
Tech stack
lua
Domain
performancedeveloper experience
Issue type
Bug
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
4
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
Over 1 week
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Stale
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
LuaNeovim APILSPAsynchronous programming
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
20