Optimize move-analyzer: it's clunky and memory hungry

[robert-zaremba]

move-analyzer often consumes at least 6GB of memory for small codebase, and it grows quickly for larger codebase. At this point is not usable. It's clunky.

If I open 2 Move projects (identified by Move.toml) - which is often in our case, as we import packages, then the memory consumption doubles and the whole experience is even worse.

Recently everyone in our team opted out from using move-analyzer because it was counter productive.

Editors that we use: Emacs, VS Code (with the move ide extension).

[github-actions]

Thank you for opening this issue, a team member will review it shortly. Until then, please do not interact with any users that claim to be from Sui support and do not click on any links!

[robert-zaremba]

Related to: #23226

[zihehuang]

@awelc

[awelc]

@robert-zaremba, have done some work on it somewhat recently so memory consumption should be better than, say, 3 months ago. That being said, I am aware of the problem not being completely solved and I am working on a solution as we speak. Stay tuned!

[awelc]

In particular, the newest version (VSCode extension v1.0.33 and move-analyzer v1.60.0) should at least prevent doubling memory consumption

[robert-zaremba]

Thanks for working on it.
TBH, it's still clunky.

[awelc]

Thanks for working on it. TBH, it's still clunky.

If there are additional missing features or things that do not work, please report using the new GitHub issue template we put together recently

[awelc]

Please checkout the new version (VSCode extension v1.0.34 and move-analyzer v1.62.0). There should be noticeable improvement already but more optimizations are coming