Fork me on GitHub
#vim
<
2021-11-07
>
sheluchin12:11:41

My clojure-lsp process takes quite a bit of memory and occasionally gets very heavy on CPU usage. Is that to be expected? Any practical ways to limit how much resources it uses without compromising its functionality too much?

ericdallo14:11:44

Not really, it actually uses high CPU/mem only during startup to analyze the project

ericdallo14:11:05

After that it caches for next startups and should not cause that much

mjw20:11:14

Has anyone in Vim land had success incorporating the experimental add-libs from clojure.tools.deps.alpha into their workflow? I have an alias in my deps.edn that I'm including when I start my iced repl, and add-libs is available in my app code, but when I try to require ring and start a jetty server, the server responds only with “empty response” errors until I restart the repl and trigger a proper download of all dependencies. I'm sure the problem is entirely between my chair and keyboard, but I'm currently blanking on a solution.

practicalli-johnny13:11:29

This is how I hotload libraries with add-libs, I use Emacs although this approach should be editor agnostics. Make sure the add-libs dependency is being loaded when initially running the REPL process. https://practical.li/clojure/alternative-tools/clojure-tools/hotload-libraries.html

mjw14:11:37

Thanks, I think there's probably something wrong with how I'm bringing it in. I've noticed a ""failed to load the S3TransporterFactory class" warning in the iced stdout buffer that I didn't notice before. I'm trying to understand that better now.