Skip to content
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

VSCode is very slow on my system #12087

Closed
miladghiravani opened this issue Sep 15, 2016 · 27 comments
Closed

VSCode is very slow on my system #12087

miladghiravani opened this issue Sep 15, 2016 · 27 comments
Assignees
Labels
*duplicate Issue identified as a duplicate of another issue(s) freeze-slow-crash-leak VS Code crashing, performance, freeze and memory leak issues
Milestone

Comments

@miladghiravani
Copy link

  • VSCode Version: 1.5.2
  • OS Version: Windows 8.1 Enterprise 64-bit

Steps to Reproduce:

  1. Please try to run vsCode faster than now.
  2. Enable drag selected text to move it (See this: http://stackoverflow.com/questions/33858029)
@bpasero
Copy link
Member

bpasero commented Sep 19, 2016

@mghhgm can you share more details about 1. and create a separate issue for 2. please

@bpasero bpasero added the info-needed Issue requires more information from poster label Sep 19, 2016
@bpasero bpasero added this to the Backlog milestone Sep 19, 2016
@bpasero
Copy link
Member

bpasero commented Sep 24, 2016

A number of days has past without answer on the questions asked. I am thereby going to close this issue to clean up our backlog of issues. Once you can answer on the questions, the issue can be reopened again. Thanks for understanding this process!

@bpasero bpasero closed this as completed Sep 24, 2016
@miladghiravani
Copy link
Author

Hi dear Benjamin!
Excuse me for the delay in response.
Details for problem 1:

  • for example when I running vscode, after 14 sec ready to use... .
  • when I openning some files and switch between them, after 2 sec ready to use... .
  • when I selecting some characters by mouse in files, this process have delay.

I compare vscode by notepad++. I programming by notepad++ for 6 years. now I use vscode for best user interface and nice themes and some features. But I like the load speed of vscode, such as notepad++.

@bpasero bpasero changed the title run slow & not enable to drag selected text VSCode is very slow on my system Sep 25, 2016
@bpasero bpasero reopened this Sep 25, 2016
@bpasero
Copy link
Member

bpasero commented Sep 25, 2016

I wonder if this issue is being caused by an installed extension. Can you try to run VS Code without extensions? From the command line, execute: code --disable-extensions and try your steps again to see if it reproduces. If you see it is an issue with the extension, please file it against the extension repository itself.

@miladghiravani
Copy link
Author

I instead of disable extensions, delete them and select default color theme but now after 12 sec vscode is ready. Please check this.
I before installed this extensions:

  1. HTML Class Suggestions
  2. Color Picker
  3. beautify
  4. PHP Symbols
  5. vscode-icons
    Thank you

@bpasero bpasero added the freeze-slow-crash-leak VS Code crashing, performance, freeze and memory leak issues label Sep 25, 2016
@bpasero
Copy link
Member

bpasero commented Sep 25, 2016

@mghhgm can you open Code window and select "Reload Window" from the command palette (press F1) and see how fast the window is loading then?

@miladghiravani
Copy link
Author

@bpasero after "Reload Window", after 9~10 sec vscode is ready. (extensions are disable)
How long after, the vscode is available for you?

@bpasero
Copy link
Member

bpasero commented Sep 26, 2016

Ok good to hear because this makes sense to be profiled and find out where most time is spend. Can you follow below steps and after starting profiling to the reload action and when everything is loaded stop the profiling?

To create a CPU profile using developer tools in VS Code:

  • select Help > Toggle Developer Tools
  • click on Profiles
  • click the start button
  • do whatever you need to do to get the CPU spin high
  • wait for some time (10-20 seconds should be enough)
  • stop the profiling
  • click the save button and attach the output file to this issue

@miladghiravani
Copy link
Author

I do this:
CPU-20160927T104738.cpuprofile.txt

Thank you

@bpasero
Copy link
Member

bpasero commented Sep 27, 2016

@mghhgm thanks so much for the report, we have an idea what it could be.

@joaomoreno fyi

@chrmarti
Copy link
Contributor

Any way to tell if #12503 is related?

@joaomoreno joaomoreno added bug Issue identified by VS Code Team member as probable bug and removed info-needed Issue requires more information from poster labels Sep 27, 2016
@bpasero
Copy link
Member

bpasero commented Sep 27, 2016

@chrmarti telling users to run a profile helps:

To create a CPU profile using developer tools in VS Code:

  • select Help > Toggle Developer Tools
  • click on Profiles
  • click the start button
  • do whatever you need to do to get the CPU spin high
  • wait for some time (10-20 seconds should be enough)
  • stop the profiling
  • click the save button and attach the output file to this issue

@bpasero bpasero removed their assignment Sep 29, 2016
@isidorn
Copy link
Contributor

isidorn commented Sep 30, 2016

Not a regression, impact low-ish, risky to change in endgame pushing to october

@isidorn isidorn modified the milestones: October 2016, September 2016 Sep 30, 2016
@miladghiravani
Copy link
Author

I think vs code is slowly because this user interface is HTML. When I open Toggle Developer Tools and select an element in the page to inspect it, see all things on vs code user interface is HTML tags ... .
ashampoo_snap_2016 09 30_12h13m04s_001_

@joaomoreno
Copy link
Member

@miladghiravani The entire VS Code interface is HTML.

We know what the cause for your issue is and will fix it next month.

@miladghiravani
Copy link
Author

Hi,
In version 1.6.1 , vs code is ready after 7 sec. (~ 46% better)
Is possible better than this?
I can't send CPU profile because this.
Thank you

@joaomoreno
Copy link
Member

Nothing really changed in the code path specific to the problem your CPU profile indicated.

@joaomoreno
Copy link
Member

@miladghiravani Can you take a screenshot of a recent CPU profile?

Is there anything special about your system? Is it a VM? Is it an enterprise managed machine?

@miladghiravani
Copy link
Author

@joaomoreno CPU profile have very lines (more than 80 fullscreen images) but I select all and copy them.
See this: cpu.txt
My system is Sony laptop and I have Windows 8.1 Enterprise 64-bit.
(For example Photoshop cc 2015 after 11 ~ 12 seconds is ready.)

@joaomoreno joaomoreno removed the important Issue identified as high-priority label Oct 27, 2016
@joaomoreno
Copy link
Member

Seems to be much faster now. Do you still experience the 7 seconds of lag as previously mentioned?

I'd like us to try something. Make sure you have Node 6.5 for this. Create a ssl.js file with the following contents:

'use strict'
const https = require('https');
const startTime = new Date().getTime();
https.get('https://marketplace.visualstudio.com', res => {
  console.log(res.statusCode);
  console.log(new Date().getTime() - startTime);
});

Then, from the command line, run it with the --prof flag:

node --prof ssl.js

What was the output or running that?

This command will also generate a isolate-*-v8.log file. Create a profiling report from it with:

node --prof-process isolate-*-v8.log > profile.txt

And send me the contents of profile.txt.

Here's mine, as a reference point: profile.txt

@miladghiravani
Copy link
Author

@joaomoreno I told "in version 1.6.1 , vs code is ready after 7 sec. (~ 46% better)"
My Node is v6.5.0
After node --prof ssl.js , see this:
200
1927

And profile: profile.txt

@joaomoreno
Copy link
Member

joaomoreno commented Oct 27, 2016

You somehow missed the --prof-process step. Here it is for reference:

profile2.txt

I will run the same on another Windows machine so we can compare.

@joaomoreno
Copy link
Member

And here is my profile:

profile_joao.txt

@joaomoreno
Copy link
Member

The profiles don't tell us much except that my script runs in 68 ticks while yours takes 1459 ticks. Both show that most of the time is spent inside ntdll.dll.

Are you inside a corporate network?

@miladghiravani
Copy link
Author

@joaomoreno
Are you inside a corporate network?
No. I use home network but Xampp is running on my system.

New profile: profile.txt is correct?

@bpasero
Copy link
Member

bpasero commented Nov 17, 2016

@miladghiravani can you try our latest insider build (http://code.visualstudio.com/Download#insiders), start it and then from the command palette run "Startup performance" and send the output from the console?

@joaomoreno
Copy link
Member

Closing as duplicate of #16065

@joaomoreno joaomoreno added *duplicate Issue identified as a duplicate of another issue(s) and removed bug Issue identified by VS Code Team member as probable bug labels Nov 30, 2016
@vscodebot vscodebot bot locked and limited conversation to collaborators Nov 18, 2017
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
*duplicate Issue identified as a duplicate of another issue(s) freeze-slow-crash-leak VS Code crashing, performance, freeze and memory leak issues
Projects
None yet
Development

No branches or pull requests

5 participants