Interview
summary
Claim: making .NET faster saves server licenses, reduces CPU heat and even helps the planet. Concrete tools: Visual Studio profiler, most broadly purview, dot and trace. Typical culprits: excessive or unnecessary locks, wrong data structures (use Dictionary or HashSet instead of linear searches), heavy allocations that push time into GC. Triage: check if the process is CPU bound via the interval/CPU metric then either continue CPU work or investigate I/O. Correctness outranks perf; keep tests green.
AI-written summary · about
chapters (6)
- 0:00Intro
- 0:20Why writing high performance code matters
- 0:58Tools to investigate performance
- 1:50Common performance problems
- 2:40Basic steps to improve performance
- 3:30correctness or performance
related talks
42mMeasure Twice, Optimize Once: Real-World .NET Profiling with Visual Studio
55mMicro-optimizations in the .Net World
57mDon’t need to understand the details of .NET. Until you do
01h 06mGet Better App Performance with this One Weird Trick
19mProfiling Your Code: 5 Tips to Significantly Boost Performance
01h 01mBeyond step-by step debugging in Visual Studio
23mThe Intelligent Development Environment
53mWhy Is My C++ Build So Slow? Compilation Profiling and Visualization