🐢 App feels slow... but WHICH process is guilty? 🔍⚡
This is a dev post classified by Jev as Testing & observability (a tutorial), kept by the Dev Radar because it carries real work, not commentary.
🐢 App feels slow... but WHICH process is guilty? 🔍⚡ This deep dive shows how to hunt hidden latency across a distributed .NET app using Visual Studio Performance Profiler + GitHub Copilot Profiler Agent. Trace requests across Blazor, services, databases, AI endpoints, and separate CPU-bound work from wait-time bottlenecks. 🤯 Ready to profile smarter? 👇 📖 Read the blog: https://msft.it/6013akVud
Posted by Visual Studio (535.6k followers) 1 days ago · 15 likes · 6.1k views · view the original post on X. Kept by the Dev Radar as Testing & observability.
More dev work like this
- What does observability look like when a judgment costs nothing? — @hugorcd
- When agent traces turn into a debugging pile, this repo gives you a place to inspect them. — @DanKornas
- I’m glad @strawgate's standards for coffee are lower than his standards for code review… — @kayvz
- Gitar finds bugs, fixes them under your team's rules, and verifies every fix by running… — @SonarSource
- OPENAI 🔥: Chrome extensions are now supported in the ChatGPT desktop browser! — @testingcatalog
- AI at scale needs visibility to match. — @splunk
- Quick tip from Visual Studio on YouTube... See the Visual Studio Debugger Agent use a… — @VisualStudio
- Agent regressions are hard to catch when traces are read-only. — @DanKornas
Every post is read and classified by Jev (TypeSafe): what it is, which market it belongs to, and whether the link is a real tool. 12.2k posts from 4.7k X accounts over the last 21 days, 1.4k tools, 12 markets. Collected every 5 minutes, fully re-ranked every hour — last update 2026-09-19 18:39 UTC. Full method.