{"id":250827,"date":"2024-10-01T07:32:23","date_gmt":"2024-10-01T14:32:23","guid":{"rendered":"https:\/\/devblogs.microsoft.com\/visualstudio\/?p=250827"},"modified":"2024-10-07T14:58:33","modified_gmt":"2024-10-07T21:58:33","slug":"visual-studio-2022-recent-performance-enhancements","status":"publish","type":"post","link":"https:\/\/devblogs.microsoft.com\/visualstudio\/visual-studio-2022-recent-performance-enhancements\/","title":{"rendered":"Visual Studio 2022 – Recent performance enhancements\u00a0"},"content":{"rendered":"

Visual Studio 2022 continues to be faster with each version. In this blog post we will highlight a couple of the more significant enhancements you\u2019ll experience in 17.11, such as a more efficient C# language service, faster conditional breakpoints and symbol searches in C++.<\/p>\n

Reduced CPU usage by C# language service<\/h2>\n

Code Indexing<\/h2>\n

In 17.10 we revamped the code indexing system in the C# language service (Roslyn).\u00a0It used to be both aggressive and highly intermittent.\u00a0 This would lead to high spikes of CPU usage, taking resources away from the operations users were performing, especially during times like solution load.\u00a0 After opening a solution, users who wanted to wait for VS to settle would have to wait up to minutes watching a progress bar titled \u201cRunning low priority background processes\u201d.<\/p>\n

Now, we no longer preemptively run all the indexers.\u00a0 Instead, individual ones are run on demand.\u00a0 In 17.11, these indexers were further streamlined, and made much more incremental, allowing them to consume far less resources when absorbing any change into the index.\u00a0In addition, there were memory allocation optimizations throughout the editor and managed language services. The net effect of this is a more responsive VS that is ready to go at a much sooner time, with much lower CPU consumption.<\/p>\n

Source Generators<\/h2>\n

As part of our continued work to break VS into isolated, high performance, services, Roslyn’s Source Generator execution host was moved out of the main VS process to a high-performance .NET 8 host.\u00a0 This helps make VS more resilient to bugs in source generators and allows them to execute much more efficiently.\u00a0 As part of this work, we also changed the execution model for source generators to no longer run automatically, due to the heavy impact that some generators can still have on the system.\u00a0 Instead, by default, generators will now run when a document is saved, or a project is built, greatly cutting down on the impact of all generators (especially very expensive ones).\u00a0 This behavior can be controlled here:<\/p>\n

Tools > Options > Text Editor > C# > Advanced > Source Generators<\/p>\n

\"A<\/p>\n

With the above changes in place, our data shows improved metrics in 17.11. CPU usage is down by 16% percent or more in sessions that had heaviest CPU usage. The C# completion list now appears sooner; looking at the slowest sessions the number of times the list takes longer than 0.5 seconds to appear has been cut by about 40%.<\/p>\n

Improved conditional breakpoint performance<\/h2>\n

In 17.11 we made several changes to improve the performance of conditional breakpoints in C++. The improvements were primarily in two categories:<\/p>\n