\u00a0<\/strong><\/p>\n Contents<\/strong><\/p>\n \u00a0<\/strong><\/p>\n The Instrumentation tool has undergone significant improvements, making it faster and more versatile than ever before. Now, it supports C++ code, enhancing the capabilities for performance analysis. The Instrumentation Data View displays a list of functions ordered by duration, streamlining the identification of potential bottlenecks.This feature was inspired by the Developer Community suggestion: Profiling \/ Instrumentation of C++ CMake application quits immediately with no data captured <\/a><\/p>\n Another noteworthy addition is the “Start with collection pause” option, enabling the temporary suspension of data collection during application profiling. This feature proves especially advantageous in scenarios like gaming, where users prefer full immersion before data collection commences. This feature was inspired by the Developer Community suggestion: Support pause for Instrumentation Profiling<\/a><\/p>\n <\/p>\n Learn More from our documentation: Analyze CPU usage in the Performance Profiler – Visual Studio (Windows) | Microsoft Learn<\/a>.<\/p>\n You can easily access the .NET Counter from the diagnostics window by picking the “.NET Counters” option from the “Select Tool” dropdown menu. You can also use the features of .NET Counters to monitor and evaluate important performance metrics while you are debugging your code.<\/p>\n .NET Counters tool brings integration with the .NET Meters API, introducing two new instrument options: “Counter” and “ObservableCounter”. The “Counter” keeps track of a value changing over time, with the caller reporting updates using “Counter<T>.Add.” In contrast, the “ObservableCounter” is like the Counter, but the caller takes care of keeping track of the total value.<\/p>\n You can find these metrics in the list of the .NET counter metrics roster, offering enhanced visibility into system performance and resource utilization.\nThis feature was inspired by the Developer Community suggestion: \u00a0Performance Profiler: .NET Counters should support custom counters <\/a><\/p>\n Additionally, the .NET Object Allocation tool has been enhanced to seamlessly import allocations from a .NET data provider through ETL file formats. This will help you analyze allocation events and monitor memory usage effectively.<\/p>\n Learn more about .NET allocation tool: Analyze memory usage for .NET objects <\/a><\/p>\n Profiling tools now support live graphs while collecting from dotnet-monitor for WSL. The WSL live metrics are available for .NET object allocation, CPU usage, and the .NET counter tool. While the tool is initially collecting data from dotnet-monitor for WSL you can see the real-time graphing for live counter information, then you can stop collecting and see detailed breakdown views of memory allocation, call trees, functions, collections, and other related data.<\/p>\n The Visual Studio Profiler has been upgraded to include support for BenchmarkDotNet IDiagnosers. These IDiagnosers are essential for efficiently gathering diagnostic data from BenchmarkDotNet scenarios.<\/p>\n The Benchmark tab offers a visualization of the executed benchmarks and provides the ability to precisely choose a benchmark from the swimlane by double-clicking on a specific row.<\/p>\n You can also navigate to the source file through the right-click context menu. The statistical data is sourced directly from BenchmarkDotNet and is presented in a structured grid format.<\/p>\n We have introduced an updated Test Profiling capability in Visual Studio 2022. When you right-click on your test in Test Explorer and select \u201cProfile,\u201d you can now choose from a set of available tools, including CPU Usage, GPU Usage, File IO, .NET Async, and Events Viewer. Simply select the tools you want to use, click \u201cStart,\u201d and a report will be generated for you. This feature provides a powerful and convenient way to analyze the performance of your tests and identify potential issues.\nLearn more about Test Profiling from our recent blog: A unit of profiling makes the allocations go away – Visual Studio Blog (microsoft.com)<\/a><\/p>\n This feature is only available in our Visual Studio Enterprise Version. Download Here<\/a><\/p>\n Our team has dedicated additional resources to enhance reliability and performance across various tools, with notable improvements in the Performance Profiler’s stop collection functionality. 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\u2019ve 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.<\/p>\n Thank you for entrusting us with your needs and aspirations. We will keep working on our Profiling tools to make your Profiling experience smoother and more efficient.<\/p>\n If you have any thoughts or suggestions, please share them with us on the Developer Community<\/a> site. Your feedback is very important to us.<\/p>\n Learn more about these and other features in Visual Studio\u2019s Profiling tool by checking out additional resources.<\/p>\n Stay connected with the Visual Studio team by following us on Twitter @VS_Debugger<\/a>, Twitter @VisualStudio<\/a>, YouTube, and LinkedIn.<\/a><\/p>\n <\/p>\n","protected":false},"excerpt":{"rendered":" In retrospect, the past year our team was on a mission to enhance Profiling tools, making them more efficient and user-friendly. We improved instrumentation and our .NET counter tool, broadened platform support, seamlessly integrated unit test profiling, and boosted overall performance. Your valuable feedback via Developer Community was crucial in making Visual Studio’s profiling experience […]<\/p>\n","protected":false},"author":26573,"featured_media":247065,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"_acf_changed":false,"footnotes":""},"categories":[155],"tags":[6839,6743,6920,6815],"class_list":["post-247062","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-visual-studio","tag-developer-productivity","tag-profiling","tag-test-profiling","tag-visual-studio-2022"],"acf":[],"blog_post_summary":" In retrospect, the past year our team was on a mission to enhance Profiling tools, making them more efficient and user-friendly. We improved instrumentation and our .NET counter tool, broadened platform support, seamlessly integrated unit test profiling, and boosted overall performance. Your valuable feedback via Developer Community was crucial in making Visual Studio’s profiling experience […]<\/p>\n","_links":{"self":[{"href":"https:\/\/devblogs.microsoft.com\/visualstudio\/wp-json\/wp\/v2\/posts\/247062","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/devblogs.microsoft.com\/visualstudio\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/devblogs.microsoft.com\/visualstudio\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/visualstudio\/wp-json\/wp\/v2\/users\/26573"}],"replies":[{"embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/visualstudio\/wp-json\/wp\/v2\/comments?post=247062"}],"version-history":[{"count":0,"href":"https:\/\/devblogs.microsoft.com\/visualstudio\/wp-json\/wp\/v2\/posts\/247062\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/visualstudio\/wp-json\/wp\/v2\/media\/247065"}],"wp:attachment":[{"href":"https:\/\/devblogs.microsoft.com\/visualstudio\/wp-json\/wp\/v2\/media?parent=247062"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/visualstudio\/wp-json\/wp\/v2\/categories?post=247062"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/visualstudio\/wp-json\/wp\/v2\/tags?post=247062"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}\n
\n
Boost Your Productivity with Improved Instrumentation Tool<\/h2>\n
![\"Instrumentation\"](\"https:\/\/devblogs.microsoft.com\/visualstudio\/wp-content\/uploads\/sites\/4\/2024\/02\/image-2.png\")
<\/a>\nLearn more about these enhancements in our recent blog: Improving Visual Studio performance with the new Instrumentation Tool – Visual Studio Blog (microsoft.com)<\/a><\/p>\n![\"Image](\"https:\/\/devblogs.microsoft.com\/visualstudio\/wp-content\/uploads\/sites\/4\/2024\/02\/new.png\")
<\/a><\/p>\nEnhancements Across Profiling Tools<\/h2>\n
.NET Counters Tool in Debugging Scenario<\/h3>\n
![\"](\"https:\/\/devblogs.microsoft.com\/visualstudio\/wp-content\/uploads\/sites\/4\/2024\/02\/17.8p1-dotnetcounters.png\")
<\/a><\/h3>\nNew Instruments via Meters API<\/h3>\n
.NET Object Allocation tool<\/h3>\n
Profiler Live Graph for .NET on WSL<\/h3>\n
![\"Image](\"https:\/\/devblogs.microsoft.com\/visualstudio\/wp-content\/uploads\/sites\/4\/2024\/02\/profiling-wsl-live-graph.png\")
<\/a><\/p>\nBenchmarkDotNet IDiagnosers<\/h3>\n
![\"Image](\"https:\/\/devblogs.microsoft.com\/visualstudio\/wp-content\/uploads\/sites\/4\/2024\/02\/17.8.p2.idiagnosers-gotosource.gif\")
<\/a><\/p>\n![\"Image](\"https:\/\/devblogs.microsoft.com\/visualstudio\/wp-content\/uploads\/sites\/4\/2024\/02\/17.8.p2.idiagnosers-swimlane.gif\")
<\/a><\/p>\n<\/h2>\n
Test Profiling<\/h2>\n
<\/h2>\n
Faster and More Reliable Profiling Tools<\/h2>\n
![\"Image](\"https:\/\/devblogs.microsoft.com\/visualstudio\/wp-content\/uploads\/sites\/4\/2024\/02\/Picture4.png\")
<\/a><\/p>\nIn the Summary<\/h2>\n
\n