Skip to main content

Visual Studio 2026–The Copilot Profiler Agent

Yes! The new Visual Studio 2026 edition is available in preview (now called Insiders). I'll take some time this week to walk through some of the features I like and maybe some of the rough edges I discover along the way.

One feature that is really new and only available inside VS 2026 (at the moment of writing this post) is the new Copilot Profiler agent. The profiler agent should be of assistant in any of the following tasks:

  • Analyzing CPU usage, memory allocations, and runtime behavior

  • Surfacing bottlenecks in your code

  • Generate new BenchmarkDotNet benchmarks

  • Validate fixes with before/after metrics, all in a smooth guided loop

  • And more…

A good introduction of the profiler agent can be found here:

But of course, we want to try it ourselves…

Hello profiler!

I have an existing set of BenchmarkDotNet test that I use to evaluate the performance of some features I’m working on and also to avoid that any change negatively impacts our performance baseline.

Let’s see what suggestions the profiler agent brings to the table:


It first asks me to install some extra diagnosers to provide Visual Studio integration. We confirm to continue:

Unfortunately, it failed afterwards probably due to an incompatibility between the newly installed diagnoser and our used BenchmarkDotNet version.

After confirming that I had indeed the latest BenchmarkDotNet version installed and a few retries with the same result, I decided to go for the power option and restarted Visual Studio.

When I asked the same question to the profiler, this time it started a profiling session. Unfortunately it didn’t look at the benchmark test I was pointing to but instead started my application.

After stopping the profiling session, the results were analyzed by the profiling agent and I got some suggestions for improvements.

A strange thing I noticed that it mixed the feedback from the diagnostic session with a feedback about the code (this time looking at the benchmark test I was hoping he would run).

 

After doing one last attempt, I had the problem with the Diagnoser again. I’ll try to fix that first before I try this feature again…

Sidenote: The BenchmarkDotNet template

While evaluating the profiling agent I noticed that the BenchMarkDotNet project found its place among the available templates. Visual Studio scaffolds a fully configured project, complete with benchmark setup and diagnosers.

 

More information

Democratizing Performance: The Copilot Profiler Agent in Action on Real Code - Visual Studio Blog

(352) Copilot Profiler Agent - YouTube

Popular posts from this blog

Azure DevOps/ GitHub emoji

I’m really bad at remembering emoji’s. So here is cheat sheet with all emoji’s that can be used in tools that support the github emoji markdown markup: All credits go to rcaviers who created this list.

Kubernetes–Limit your environmental impact

Reducing the carbon footprint and CO2 emission of our (cloud) workloads, is a responsibility of all of us. If you are running a Kubernetes cluster, have a look at Kube-Green . kube-green is a simple Kubernetes operator that automatically shuts down (some of) your pods when you don't need them. A single pod produces about 11 Kg CO2eq per year( here the calculation). Reason enough to give it a try! Installing kube-green in your cluster The easiest way to install the operator in your cluster is through kubectl. We first need to install a cert-manager: kubectl apply -f https://github.com/cert-manager/cert-manager/releases/download/v1.14.5/cert-manager.yaml Remark: Wait a minute before you continue as it can take some time before the cert-manager is up & running inside your cluster. Now we can install the kube-green operator: kubectl apply -f https://github.com/kube-green/kube-green/releases/latest/download/kube-green.yaml Now in the namespace where we want t...

Podman– Command execution failed with exit code 125

After updating WSL on one of the developer machines, Podman failed to work. When we took a look through Podman Desktop, we noticed that Podman had stopped running and returned the following error message: Error: Command execution failed with exit code 125 Here are the steps we tried to fix the issue: We started by running podman info to get some extra details on what could be wrong: >podman info OS: windows/amd64 provider: wsl version: 5.3.1 Cannot connect to Podman. Please verify your connection to the Linux system using `podman system connection list`, or try `podman machine init` and `podman machine start` to manage a new Linux VM Error: unable to connect to Podman socket: failed to connect: dial tcp 127.0.0.1:2655: connectex: No connection could be made because the target machine actively refused it. That makes sense as the podman VM was not running. Let’s check the VM: >podman machine list NAME         ...