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

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 ...

Cache stampede: when our cache turned against us

While investigating some performance issues, we ran into an ASP.NET Core API that cached a fairly expensive aggregation query for 60 seconds. Under normal load, that was fine: one request rebuilds the cache, everyone else reads from it. Under peak load, dozens of requests would arrive in that same expiry window, all see a cache miss, and all fire the same expensive query in parallel. The database didn't like that. That was the moment when our caching layer stopped helping and started hurting. A burst of requests comes in at the same time, all miss the cache, and all go hammer the database or the downstream API at once. That's a cache stampede . The cache was supposed to protect our backend, and for a few hundred milliseconds it did the opposite. Why this happens IMemoryCache.GetOrCreate (and its async sibling) looks like it protects you, but it doesn't add any locking on its own. Look at the naive version: public async Task<Report> GetReportAsync(string key) ...

A complex system designed from scratch never works

A few years ago, I worked as an architect on a big mainframe rewrite. I still count it as one of my failures. Not because the technology was wrong, but because I couldn't convince the management team to simplify the approach. Years later, the organization is still struggling to get the new system up and running. I left the project at the time, because I couldn't put my name behind an approach that would take very long and cost a lot of money without a working system to show for it along the way. Gall’s Law That memory keeps coming back to me, because it's a textbook case of Gall's Law playing out in real life. Gall's Law , from John Gall's Systemantics , states it plainly: A complex system that works is invariably found to have evolved from a simple system that worked. A complex system designed from scratch never works, and it cannot be patched to make it work. You have to start over with a simple system that works. What does that mean in practice,...

The art of simplicity

Search This Blog