David Barsky

> [@davidbarsky](https://github.com/davidbarsky) After disabling cache priming, rust-analyzer now only takes 5.5GiB of memory. It's also much faster to start, so I think I'm never going back 😄 I'm guessing you...

> That test failure is not good, I can't reproduce that on windows ... any mac users here? Yeah, I can check in a few hours.

> There is a couple of queries being recomputed here which seems odd. I think this might be ast id collisions happening on mac only ... I think the test...

This probably depends on using the new trait solver in rust-analyzer. We're working on it, but it'll take some time.

> but the interesting part is that RA doesn't error out or crash with its beloved textDocument/completion failed. The two are unrelated: if you see a visible panic, that's a...

I think persistent caches for rust-analyzer are still a nice-to-have that require a _lot_ of design work before they're implemented. In the meantime, I recommend using ra-multiplex.

> Not sure I fully understand this, but if I do, then I think this is caused by the VFS being processed fairly slowly. I think the VFS is partly...

> Memory use is also a problem, as it can lead to swapping and thrashing. According to `gnome-system-monitor`, RA uses **~380MB** on my system (4GB RAM), and I've literally just...

What sort of values/configuration are being set by your extension? Is it some build configuration/project discovery stuff, or...?

`RUSTFLAGS` can only be set by the end user; we cannot say how different the environment variables are different without seeing your environment, unfortunately.