2
votes

Continuation question from: VS2010 loads slowly. Can I profile extensions' respective startup time?

After looking at the log file, it turns out there are a few packages that I'm not using much (I think):

  • (load time) (package):

  • (2s) (Microsoft.VisualStudio.TeamArchitect.DesignersCommon.DesignersCommonPackage, Microsoft.VisualStudio.TeamArchitect.DesignersCommonPackage, Version=10.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a)

  • (4.2s) (Microsoft.VsWizards.ImportProjectFolderWizard.NewProjectFromExistingPackage, Microsoft.VisualStudio.ImportProjectFolderWizard, Version=10.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a)
  • (1.8s) (Microsoft.Xna.GameStudio.XnaPackage, Microsoft.Xna.GameStudio.Core, Version=4.0.0.0, Culture=neutral, PublicKeyToken=6d5c3888ef60e27d)

and one very strange query that takes 3.7s:

Calling ReleaseService::Search whereClause : (Project.Metadata['VsixId'] = '4d4b29b7-971b-4ff2-8604-cf9f67fbb705') AND ((Project.Metadata['SupportedVSEditions'] LIKE '%10.0,IntegratedShell;%') OR (Project.Metadata['SupportedVSEditions'] LIKE '%10.0,Pro;%') OR (Project.Metadata['SupportedVSEditions'] LIKE '%10.0,Premium;%') OR (Project.Metadata['SupportedVSEditions'] LIKE '%10.0,Ultimate;%')) orderByClause : skip : take :

Do you have any ideas how to reduce their times? Is there a location where I can selectively choose these packages to be loaded only when required?

1

1 Answers

1
votes

Do you have any ideas how to reduce their times?

There is a way to improve load times without disabling the packages. This is universal way of speeding up program load but you need to have an SSD.

1) Find out what folders are being hit most heavily during startup. ProcessMonitor from SysInternals can visualize it. In VS 2010 case these folders on my box were:

C:\Program Files (x86)\Microsoft Visual Studio 10.0\Common7\Ide\ C:\Users\\AppData\Local\Microsoft\VisualStudio\10.0\Extensions

2) Move this folders to SSD.

3) Create NTFS Junction from old folder location to the new one: mklink /J (mklink is not an .exe - it's a command build-in into cmd.exe)

Also you could try to disable packages from Tools/Extensions. But from my experience VS start up time improves only if you skip all extensions. IMHO it's studio extension engine that takes a lot of time to start and slows the studio startup, not the extensions.