If you find that some of them are taking over 1000 milliseconds to start, you may want to investigate this further. Once you hit enter, you will be able to see a list of your currently running extensions, and the start-up time in milliseconds of each. To open the Command Palette, use the shortcut for your platform: All you have to do is open the Command Palette, and enter the command: "Developer: Show Running Extensions" VS Code has a cool feature where you can see exactly how long each of your extensions took to start up. This will give you some confidence in knowing whether or not your problem is the result of an extension. Keep doing this until you've gone through all of your extensions. files take 2 sec to open) than this should be quite easy.ĭisable → test → enable → disable the next one → test → etc. If your performance issues are obvious (E.g. Here's how to do it: Simply disable your extensions one at a time, and check to see if it made a difference. There is one powerful technique you can use however which may reveal if an extension is what's causing your problem. It's hard to tell exactly what's going on with your extensions unless you dig into the source code. (This is probably a good practice anyway) Quality: Is one of your extensions poorly optimized? If you have 20+ extensions installed, it may be a good idea to disable some less necessary ones and see if it makes a difference. Quantity: How many extensions do you have? 3rd-party plugins are always a good first spot to check for performance issues. The problem is that some extensions may be poorly programmed and put more strain on your system than necessary. After retrieving your version, simply go to google and type in "VS Code latest version" Are extensions causing the poor performance? The first version number listed will tell you which version you're running on.
If we can't do that, it's going to be very hard to fix anything. We have to understand what's causing it in the first place.
This is the first step to fixing the problem.
0 kommentar(er)
