Visual Studio 2022 – 17.6 Performance Enhancements

Nayana Srikanth

Visual Studio 2022 17.6 introduces exciting performance enhancements in several key areas. These improvements aim to enhance the overall software development experience by boosting productivity, reducing wait times, and providing a smoother workflow.

The performance enhancements in Visual Studio 2022 17.6 include:

You can download Visual Studio 2022 from the Visual Studio downloads page or upgrade your existing installation by following instructions on the Update Visual Studio page. 

Solution Open

Significant enhancements have been made to Solution-Open performance and Solution Filters, particularly for larger projects. Testing with the Chromium repository, which consists of 11000 projects, showed a remarkable 8x faster cached project load time, saving 3.5 minutes in Solution Load time. The cached Chromium solution now loads in approximately 30 seconds. Additionally, for a Solution Filters scenario with 63 projects, Chromium loads in just 20 seconds, which is 3x faster. These enhancements greatly benefit larger projects, enhancing productivity and reducing loading times. 

Image SolutionOpenChromiumAllsln black

 

Solution Close 

Enhancements have been made to the Solution-Close process, which notably accelerates closing a solution with C++ projects. These improvements provide a 20% to 50% speed boost in closing solutions, depending on their size, with the most significant performance gains observed in larger projects (1000+ projects). For instance, in Chromium projects, the improvements result in a 50% acceleration, saving around 20 seconds of time. 

Image SolutionCloseChromiumAllsln black

 

Git File History 

 We are pleased to announce that the Git History feature in Visual Studio has been enhanced to provide faster loading times for file and folder scenarios. Git repositories with longer history and more time between commits will see greater speed improvements. We’re excited to share that our measurements indicate a 42% improvement in the Git public repository. 

Image 17 6 git log demo 2 1

 

 

Image Githistory new black1

 

Git Branch Switches 

We’ve further reduced the time it takes to switch between git branches in Visual Studio by optimizing file system changes detection and processing. Additionally, we’ve enhanced the way Visual Studio handles calls to git for this specific case.  

Image Gitbranchswitch

 

Lightbulb Improvements  

The lightbulb/code actions have been greatly improved through comprehensive redesign of the diagnostics and code analysis architecture.  We have focused on optimizing all components involved in bringing up a lightbulb through a combination of low/medium/high level fixes. 

  • Low-level fixes included limiting tree walks, improving string handling, optimizing source text handling, reducing allocations, and optimizing data structure-level optimizations in the diagnostics code paths. 
  • Medium-level fixes included cancelling background diagnostics (squiggles) when computing Lightbulb diagnostics, optimizing background indexing, limiting analyzers that are applicable per document, addressing inefficiencies in several 1st party/2nd party analyzers like PublicAPI analyzer, and improving our caching model. 
  • High-level fixes included a complete overhaul of the diagnostics pipeline to answer span-oriented questions, infer which analyzers are applicable to run on specific spans, and deprioritize slow analyzers based on historical run. 

Before

Image Before

After

Image After edit

 

 

We have made substantial enhancements to the performance of both the CPU and memory, specifically when dealing with extensive source files. We have successfully minimized the number of progress bar cycles required for the Lightbulb scenario in a large source file. Previously, it took approximately 8 to 17 cycles, but now we have reduced it to less than one cycle, as illustrated in the above gif.

 

Performance Profiler Stop Collection

The stop collection feature of the Performance Profiler has undergone performance improvements recently. These enhancements include implementing parallel NGEN PDB creation, parallel C# metadata scraping, and NGEN PDB caching in the symbol cache. As a result, metadata loading time and debug symbol loading time for NGEN PDBs have significantly decreased.  

 The stop collection now runs approximately 3.5 times faster when generating and almost 15 times faster when using cached values (which are always used if available). We’ve tested this using a 10-second trace in Visual Studio, and version 17.6 demonstrates a considerably faster performance than previous versions 17.5 and 17.4.  

Image StopCollection 1

 

Image Profiler

 

Tell us what you think! 

We hope these performance enhancements make your development work efficient and enjoyable. Feedback from developers like you is very important for us to improve the product and meet your expectations. We welcome your feedback on Visual studio performance. The preferred approach is using the Report-a-problem tool. You can also leave comments below. 

 

 

 

10 comments

Comments are closed. Login to edit/delete your existing comments

  • Rand Random 2

    Consider deleting gif of topic „Lightbulb Improvements„ – „After“ as it seems to contain personal data (discord chat)

  • Mystery Man 0

    I cannot fully install Visual Studio 2022 v17.6 because the download of IncrediBuild fails. The hosting website returns a 403 error.

  • Mike M 2

    @nsrikanth Visual Studio has become a memory hog… what is being done to mitigate the issue?

    • mathieu prevot 1

      Unless there is a memory leak, using more memory means using less CPU or hard drive, so this is rather good news.

  • Richard Deeming 3

    Unfortunately, it also includes the “performance enhancement” of doubling every key press in a JavaScript block within a CSHTML file. 🙁

    That saves you time when you have to type the same character twice, at the “minor” inconvenience of having to press backspace after every character you only want to type once.

    As it stands, this version is unusable for ASP.NET projects; I have to switch to VS Code every time I want to edit a view.

    • Ian Marteens 0

      It’s an old bug, but it shows from time to time. Never bothered myself with reporting it. Thanks for doing it, Richard.

  • mathieu prevot 2

    the performance improvement on lightbulb and profiler are very much welcome ! opening and closing solution too !

  • Alexander Preslavski 0

    Are there any known issues with compiling blazor projects using this version as I am experiencing broken components after upgrading the VS version?

  • Hamed 1

    This is what I want to see from Visual Studio team, performance is (maybe was) the main area vs falls behind vs code and other IDEs.
    Keep up the great work!

  • David 1

    These perf improvements are very welcomed from my side.

    I think there is a need for a lightweight mode where we would get rid of “fancy” useless features which get in our way.

Feedback usabilla icon