salesforcedx-vscode: Apex Extension not loading before it can be activated (high CPU usage)

We have taken several steps to better optimize the Apex language server. From our internal testing & benchmarks, we see significant improvement. For large projects running on machines with limited horsepower, you can still see some latency & performance issues. (Documentation forthcoming that should help provide more guidance on what project size is suitable for different machine sizes.) We hope that the improvements have resolved most issues for most users, so I am closing this issue. Please open a new issue with details if you experience further Apex performance issues. Thank you to all who contributed information to help us diagnose the underlying causes!

Hi @jonathanwiesel, we are doing different things to address the different performance issues with webpack being one of the tools being used but not limited to it. We are currently refactoring the extensions in order to cut down on our dependencies. We are also working on making some of those dependencies significantly smaller.

Some of the issues are related to the language servers and not the extensions themselves, so we are currently working on profiling them and testing new changes to make the code more efficient.

HI @jamessimone and all - We released some changes in Dec and have more going out weekly over the next couple months. After some profiling and analysis, we believe the main root cause is the core extension size and some of the dependencies between the extensions. It’s not quick to unravel some of this, but we are making progress. We’ll post major updates here so you let us know if things are improving. Thanks to all who have shared data & details - extremely helpful!

salesforce.salesforcedx-vscode-apex-unresponsive.cpuprofile.txt