v0.21.1 with fix for use problem has been released
lukaszsamson
ElixirLS Core Team
lukaszsamson
ElixirLS Core Team
Version 0.22.0 has been released 
Highlights:
- Support for elixir 1.17 and new type system diagnostics
- Support for OTP 27 including process labels in debug adapter
See full release notes
ElixirLS elixir-ls/CHANGELOG.md at v0.22.0 · elixir-lsp/elixir-ls · GitHub
vscode extension vscode-elixir-ls/CHANGELOG.md at v0.22.0 · elixir-lsp/vscode-elixir-ls · GitHub
12
D4no0
I’ve been wondering why elixir-ls struggles at projects that have a lot of source files?
I currently work at a project that has in the ballpark 15k source files and elixir-ls just gets stuck, we have to resort to using lexical, which is also written in elixir.
lukaszsamson
ElixirLS Core Team
I can’t guess what is the problem. Please spend some time diagnosing it if it is impacting your productivity. A PR or an issue with repro is always welcome.
D4no0
Exadra37
It also struggles in projects with just a few files.
I am not able to always use the Go to Definition or Find References in a project where I have written less then 100 files.
At work, in a project with 19k files it’s unusable almost all the time. Lexical is better but still fails a lot.
Maybe we need to resort to an LSP server written in Rust? 
fmn
did you checked LS logs? on GNU/Linux i have it under ~/.local/state/nvim/lsp.log, and it’s a default setting.
also, it would be good to know project/code structure
here’s a curiosity:
$ mix new dummy; cd dummy
* creating README.md
* creating .formatter.exs
* creating .gitignore
(...)
$ mkdir lib/dummy
$ echo -en "defmodule Dummy do\n def f() do\n" > lib/dummy.ex
$ for i in $(seq 1 10000); do \
echo -en "defmodule Dummy${i} do\n def f() do\n ${RANDOM}${RANDOM}\n end\nend\n" > lib/dummy/dummy${i}.ex; \
echo -en " Dummy${i}.f()\n" >> lib/dummy.ex; \
done
$ echo -en " end\nend\n" >> lib/dummy.ex
$ time mix
Compiling 10001 files (.ex)
Generated dummy app
real 2m41.485s
user 7m34.029s
sys 0m29.271s
almost 3 minutes; it’s on 8 core i7-1355U.
fmn
i had such issues with ElixirLS also. couple of files, and for some reason i was waiting for 20-30 seconds for ElixirLS to work (i mostly use Neovim).
recently it is not happening for me, and i never got to the bottom of it.
Exadra37
I use Sublime Text.
At work, in the project with 19k files I end-up waiting around 10 to 30 seconds on average to save a file, and without anything enabled to run on save. I just got ride of it after reinstalling ST from scratch, including deleting configuration and cache, but after some weeks of use it got to start slowing down again. Deleting the elixr-ls folder only seems to help with getting the index to work better again.
D4no0
The project I work on, compiling it on a M3 mac pro takes about 10-15 minutes with lexical, as some files are really huge. As for looking at logs, I was doing that before I switched to lexical and there was no explicit error, I have a feeling there might be some race condition there.