-
Notifications
You must be signed in to change notification settings - Fork 391
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
❓ Ask: Help Us Gather Slow Startup Performance Data #5488
Comments
Sorry - missed that request: Windows 11 VS Code About info: |
@diyer @AnanyaJha here's the info for my machine, for non-cold activation. I'm a Salesforce employee too, so feel free to reach out to me internally if that would be helpful. startup_performance-2024-02-29.log Version: 1.86.2 (system setup) |
Thank you @jongpie! Looks like you are seeing very high load times , We will definitely reach out to you to test out few things when we have them ready to test. |
------------ Non-Cold Startup ----------------------- ---------- Log File ------------------ Salesforce Extension Version in VS Code: Salesforce Extension Pack (Expanded) v60.2.3 -------------- OS and version --------------------------------------- |
Log file VS Code Version Version: 1.87.0 (user setup) |
Non-Cold Salesforce Extension Version in VS Code OS and version: Edition: |
Hi all, the latest version of our Salesforce extensions 60.12.0 has gone through significant decrease in its size ~25% due to major upgrade to the version of @salesforce/core library. We would appreciate if you could take some time to compare this version and let us know how this impacts your startup time performance (hopefully in a good way:))! @gbickel-nuage @jongpie @paullinder-ctl @wharlen @kaustubhdapurkar @melissajhansen @salesforcekorea |
Hey @diyer, Below are the startup performance details after updating the extensions. Version: 1.89.1 (user setup) |
Hi @diyer, here are the stats from my machine. I collected 3 logs - warm with no SFDX, cold start w/ SFDX, warm start w/ SFDX. Logs
ScreenshotsSystem Info
VSCode Info
RemarksI'm glad the team is looking into performance, and it's great the team is engaging with the community for crowdsourced information. In its current state, the Salesforce extension pack is extremely inefficient, particularly the Apex extension. Every day begins with a 15-20 minute delay waiting for the extensions to load on a modern i7 machine with 32 GB RAM. This is totally unreasonable. The performance issues are not limited to startup. At times, the greedy memory usage causes other extensions, such as source control, to hang and enter an unrecoverable state. I frequently disable most SFDX extensions if I know I'll be doing a lot of search + replace or git tasks. This is unfortunate because I then lose intellisense and reference/definition links. Lastly, I think performance (mainly memory) issues are a likely root cause for other observed issues such as failed/hung starts for the Apex Language Server - see #1581, #5268 - not totally convinced, but I'm sure some of these would at least be less frequent for your user base if performance is improved. |
We've spent the past few months investigating issues with startup performance and identified a few areas of change. While we've started to make some improvements, we need some more information from you!
In order to collect startup performance numbers, we want you to do the following -
Please share cold activation vs non cold activation startup numbers. (The cold activation time is the first run of the extension after you install it. It tends to be slower than other times.)
Save the contents of Startup Performance to a file and attach the file to this issue. Also attach a screenshot of Salesforce extension startup numbers from this tab.
In addition, also provide us the following details -
Salesforce Extension Version in VS Code:
OS and version:
VS Code version:
Thanks again - your participation here will help us improve those Extension Pack load times for YOU!
The text was updated successfully, but these errors were encountered: