-
Notifications
You must be signed in to change notification settings - Fork 445
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
Activation time is too slow #257
Comments
@mtxr what is the size of your |
I don't remember exactly which file I opened that took 36k ms, but I opened a file like this one below 5 times, activation time was always around 13,5k ms. @url = *********
@username = ********
@password = *******
###
# @name login
POST {{url}}/auth/password HTTP/1.1
Accept: application/json, text/plain, */*
Content-Type: application/json
{
"username":"********",
"password":"**********"
}
###
# @name query
POST {{url}}/application/query HTTP/1.1
Accept: application/json, text/plain, */*
Content-Type: application/json
Authorization: Bearer {{login.response.body.$.data.id}}
{JSON DATA}
|
@mtxr Sorry for the late reply, I'd like to share with you some progress on this issue. I tested your http file, the average activation time was around 5s. Althought the time seems much smaller than yours, I also think this is a bit unacceptable. I dive into my code, and add some measuring code. I found that the most time-cosing steps are
|
so disabling telemetry (which should be a good citizen and be OFF by default btw) could already improve the performance now? |
@Huachao how can I get the performance starts for extensions? |
@pke maybe a built-in command named like Show Running Extensions of VSCode |
@Huachao 642ms now. Well done! |
@Huachao thank you very much! Great job! |
Take a look..
We have written the needed data into your clipboard. Please paste:
The text was updated successfully, but these errors were encountered: