Performance issues with larger repos

[Gekctek]

I wanted to share a couple repos i have that have serious vscode motoko extension performance issues
I generally just dont rely on it for errors/warnings because they either don't show up/the old errors are still showing
So i usually rely on the dfx build or mops test which are fast to run and show me the issues in my code
My theory before has been its been because of how many MOPS packages i have referenced, but have no evidence to back that up

Repos:

https://github.com/edjCase/liminal
edjCase/motoko_atproto@db97b66

[seb-icp]

I second this. Project with 20+ dependencies, each update taking a couple of seconds to propagate, showing warnings from errors that have been corrected. It looks like having MOPS packages makes it slighty worse vs local.

[marc0olo]

@rvanasa I know that we have seen performance issues in the past. I am wondering if this is still related to #173 which was supposed to be fixed with #239 🤔

[mattigrthr]

I'm also experiencing issues on a rather small repo.

I have a workspace open only for that repo.

The repo is OSS and can be found here:

https://github.com/FreeosDAO/fractal_sortition_oc_bot

These are my VSCode settings for the workspace:

{
  "files.watcherExclude": {
    "**/node_modules": true,
    "**/dist": true,
    "**/.dfx": true,
    "**/.mops": true
  },
  "typescript.tsserver.maxTsServerMemory": 16384,
  "editor.formatOnSave": false
}

Also created a post on the developer forum:

https://forum.dfinity.org/t/vscode-motoko-plugin-performance-issues/62523