Very slow on large amount of projects / Large codebases

[dakamakat]

Dont really know why but LSP is getting very slow ( unable to get any diagnostic in file or react on code changes in even 1 min ) on repos with large amount of projects ( smth like 80+ ) i use space station 14 repo to check this

NVIM 0.10.0 Release csharp_ls installed version 0.14.0

or maybe it's related to my completition plugin but it's now wery likely bc everything same when i disable it ( i use nvim-cmp )

is there anyone who experianced same issue or know workaround for this ( i was expiriencing smth similar with omnisharp as well )

[Wordluc]

i've been experiencing the same for a while now, i have not found anything to solve this. It takes about 5 minutes

[razzmatazz]

I have just implemented pull diagnostics which should help here:

• https://github.com/razzmatazz/csharp-language-server/pull/174

Would you have chance to test it if it helps in your case?

[Wordluc]

i am using Manson to manage lsp so i can't do a manual pull, it works base on version

[ichirou2910]

i am using Manson to manage lsp so i can't do a manual pull, it works base on version

You can pass custom config to Mason. Something like this:

local config = {
	cmd = { "/path/to/local/csharp-ls" },
}

mason_lspconfig.setup_handlers({
	function(server_name)
		if server_name == "csharp_ls" then
			lspconfig["csharp_ls"].setup(config)
		end
	end,
})

[dakamakat]

Tested it with latest master ( #174 implemented ) on large repo but seems situation does not changed ( at least for me ) still ~5 mins to load solution ( around 85 projects ) and ~5 min to even start to respond on changes

[Wordluc]

same thing of @dakamakat

[razzmatazz]

What interaction you mean by he word "responding"? Is it diagnostics that show up late, or completion item do not appear fast enough? I am inclined to emit requests stats to stderr periodically in debug mode to find things like these, but it would be nice to know if you have noted a particular functionality that is laggy or just the "entire experience"

[Wordluc]

It takes about 5 minutes to initialize(for large project), and during this time, the LSP doesn't respond, neovim acts like a normal editor without lsp.

[Wordluc]

would be possible to start loading the initial project (where you are currently working) and then extend the loading process to the inner project, enabling the LSP to begin working with it, even if temporarily not with full functionality?.

[razzmatazz]

Is there a solution that is being loaded or just multiple projects, sequentially? I have noticed that having a solution file that references the projects significantly reduces load time. (Presumably Roslyn loads those in parallel)

[Wordluc]

it's a solution with different projects

[Doctor-Cpu]

Downgrading down to 0.11.0 drastically improves the initial loading time for me.