SQL in the City, London, 2014: How to speed up .NET and SQL Server web apps
Download as PPTX, PDF0 likes225 views
This is an older version of this talk, that I gave at SQL in the City, in London a couple of years back. It's very much examples based and shows the tools and techniques you'll need to use to hunt down performance problems in .NET and SQL Server web applications. I have more up to date versions of this talk and, in particular, would suggest you check out the extended edition that I tend to give at user groups. This includes a section on memory management, which doesn't fit into the 50-60 minutes normally allocated for a conference slot.
Ad
More Related Content
Similar to SQL in the City, London, 2014: How to speed up .NET and SQL Server web apps (20)
Recently uploaded (20)
Ad
SQL in the City, London, 2014: How to speed up .NET and SQL Server web apps
- 1. How to speed up .NET and SQL Server web apps Bart Read
- 2. Who am I? • Bart Read, Consultant, Software Engineer • .NET, SQL Server, performance tuning, project management • Previously worked for Red Gate • Contacts • E: [email protected] • W: www.bartread.com • B: www.bartread.com/blog • T: @bart_read • GH: https://github.com/bartread
- 4. Tools of the Trade
- 5. .NET Performance & Memory Profilers
- 6. SSMS & SQL Profiler
- 7. Load Testing
- 8. SQL Server Monitoring Tools
- 10. Scenario 1 The Slow Support Centre
- 11. Customer Support Centre (MS Dynamics)
- 28. Grant Fritchey’s FREE eBook on execution plans: http://www.red- gate.com/community/books/s ql-server-execution-plans-ed-2
- 32. Scenario 2 The Memory Leak in the eCommerce Site
- 33. eCommerce Site (MS Dynamics) Other technologies: - NServiceBus - Endeca
- 40. Solution (Nasty Hack) container.Kernel.ReleasePolicy = new NoTrackingReleasePolicy(); (Creating some technical debt for the future.)
- 41. Scenario 3 Locking, Blocking and Deadlocking
- 42. Locking, Blocking & Deadlocking
- 44. Concurrency • Object level concurrency • Row level concurrency
- 46. Transaction Isolation Levels • Read Uncommitted • Read Committed <- SQL Server default • Repeatable Read • Snapshot • Serializable ACID
- 49. Locking pattern • Reads • A -> B -> C -> D -> A -> B -> C -> D -> E -> A … • Etc. • Writes • A –> B -> C -> D -> E -> A -> B -> A -> B -> C -> D … • Etc.
- 50. Solutions • DEADLOCK_PRIORITY • http://msdn.microsoft.com/en-us/library/ms186736.aspx • SET DEADLOCK_PRIORITY LOW | NORMAL | HIGH • Read Committed Snapshot Isolation • http://www.brentozar.com/archive/2013/01/implementing-snapshot-or- read-committed-snapshot-isolation-in-sql-server-a-guide/ • Disciplined ordering of object access • Unit of Work Pattern • Martin Fowler • http://martinfowler.com/eaaCatalog/unitOfWork.html
- 51. Other Scenarios • Indexes • Missing indexes • Maintenance • Statistics • NTEXT (etc.) preventing online rebuilds • http://www.bartread.com/2014/09/17/convert-all-ntext-columns-to-nvarcharmax-sql- server/ • Stored procedures and cached execution plans • WITH RECOMPILE
- 52. Questions? E: [email protected] W: www.bartread.com B: www.bartread.com/blog T: @bart_read GH: https://github.com/bartread
Editor's Notes
- #48: I also had batch started and batch completed selected further down. It’s more information than I needed to collect but, remember, like I said earlier you can export this to a database table to make it easier to work with. Generally I’d always err on the side of too much information rather than too little just because it’s a pain if you have to go back and run another profiling session later, especially if you’re in a situation like I was where access to production infrastructure is very tightly controlled.