performance improvements about vscode-motoko HOT 8 OPEN

Thanks! I will increase the priority of further optimizations (currently representing DFINITY at ETHDenver, so I'll most likely take another look at this after March 5). If anyone reading this is at the convention, definitely come say hi! :)

from vscode-motoko.

can this be improved? i autosave every 500ms (in case that has an effect)

from vscode-motoko.

Does this still happen when autosave is turned off? This looks like a bug with the type checking debounce logic (rather than purely a performance issue), so it'll be helpful to know whether this is related to autosaving.

from vscode-motoko.

I have this issue too and autosave is turned off, not sure if it could be caused by wsl2.

from vscode-motoko.

turning off autosave didn't help :/
i'm on macos and use the latest version of the plugin

from vscode-motoko.

Thanks for checking. Are there any public projects which I could use to fully recreate the issue on my end?

For some context, large projects with > 100 files used to take over a minute to fully type-check (comparable to large Rust projects in VS Code). Something on the order of 1-2 seconds is currently expected for projects with large numbers of files and dependencies. This can be further improved in the future, and hopefully the recent round of optimizations makes the extension a lot more usable for large projects in the immediate term.

from vscode-motoko.

Yes, you can check this
https://github.com/flowerpowerdao/power-equalizer

from vscode-motoko.

Version 0.13.11 of the extension includes several bugfixes and improvements to address this issue. I'll leave this issue open for a bit; if you notice a difference (or lack thereof) in the smoothness of the type checker, definitely let me know so I can determine whether to prioritize another round of optimizations. :)

from vscode-motoko.