Skip to content
This repository has been archived by the owner on Oct 13, 2024. It is now read-only.

A lot slower initialization compared to VS Code C# Dev Kit #13

Open
Imlimp opened this issue Dec 4, 2023 · 6 comments
Open

A lot slower initialization compared to VS Code C# Dev Kit #13

Imlimp opened this issue Dec 4, 2023 · 6 comments

Comments

@Imlimp
Copy link

Imlimp commented Dec 4, 2023

When I load my project in vs code it takes about 20 seconds to initialize. When I load the project in neovim is takes 5-10 minutes to initialize. Why can this be? Is this something that can be solved?

@jmederosalvarado
Copy link
Owner

Hmm, I've never experienced this on my side. How big is your project?

@Imlimp
Copy link
Author

Imlimp commented Dec 4, 2023

It is quite a large unity project. About 8000 *.cs files and 33 *.csproj files

I can also mention, if I load a small project it loads instantly. Same behaviour on multiple computers.

@Imlimp Imlimp changed the title A low slower initialization compared to vs code C# Dev Kit A lot slower initialization compared to vs code C# Dev Kit Dec 4, 2023
@Imlimp Imlimp changed the title A lot slower initialization compared to vs code C# Dev Kit A lot slower initialization compared to VS Code C# Dev Kit Dec 4, 2023
@jmederosalvarado
Copy link
Owner

jmederosalvarado commented Dec 6, 2023

if you clone your project to a different path and open it for the first time in vscode, does that first time take a long time or loads quickly?

EDIT: I think I saw something related to project snapshots in the vscode extension, so I'm trying to figure out if it's caching some project info to make it load faster.

@Imlimp
Copy link
Author

Imlimp commented Dec 8, 2023

I tried your request. The project loaded almost instantly even when it was a completely fresh directory.

Would be awesome if something like that would be possible.

@Issafalcon
Copy link

I am seeing the same issue with large codebases containing multiple projects (i.e. In my day-job on enterprise software).

It would be great to switch over to using this plugin / roslyn, but this is the only thing that prevents me from moving away from omnisharp lsp.

Have you had any luck with your caching investigations @jmederosalvarado ?

@Issafalcon
Copy link

@jmederosalvarado - So I've just tried this plugin out again to replace the omnisharp lsp, and the speed has significantly improved on the initialization on the same project I was having slow initialization times with before.

Not sure what's changed since my last comment, but kudos for you for getting this plugin in place!

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants