Making it faster
summary
Investigation shows a site that used to be fast now has random requests issuing 70+ SQL queries and a 1.5s homepage where 45% of time is spent in a recursive resolve step that triggers cache cleanup. The team collects ETW traces with PerfView/ETW, grabs memory snapshots, extracts in-process cache contents, and runs Benchmark.NET on real exported data. Root cause is a null-object pattern plus obfuscated code putting bad IDs into cache; targeted fix and validated microbenchmarks reduce latency without scaling servers.
AI-written summary · about
chapters (7)
- 0:00Start
- 13:03Latency analysis
- 16:27Dynamic profiling shows what is happening inside the process
- 32:53Crime scene - done. What does it take to write fast code?
- 34:03Understand the technology limits
- 35:40Most important part
- 35:55Maintainable modularity
related talks
36mMake It Fast
01h 09mSherlock Homepage - A detective story about running large web services
01h 06mGet Better App Performance with this One Weird Trick
01h 01mWeb Performance Deep Dive
44m.NET Performance Investigation
01h 02mWriting high performance code in .NET
01h 03mApplication Performance Optimisation in Practice
37mRock Your Code Code and App Performance for Microsoft .Net