Advanced Plan Explorer Usage for Tuning Execution Plans
summary
Plan Explorer (SentryOne) demos show concrete techniques: add parallelism operations and plan tree columns to spot 4‑thread distribution and unbalanced threads, inspect estimated vs actual to find parameter sniffing (Alaska run ~40ms vs Illinois ~4200ms), use index analysis histograms and the tipping point marker to choose seeks vs scans, apply included columns to cut key lookups (examples drop key lookups from 6 to 3 and table IO from ~40k to ~21k), and run live query profile to watch where time is spent.
AI-written summary · about
chapters (18)
- 0:00Introduction
- 1:15Disclaimer
- 1:54Agenda
- 3:25Management Studio vs Plan Explorer
- 4:33Customizing UI
- 11:02Should I be going parallel
- 14:34Reset Sorting
- 16:09Stored Procedure
- 16:43Performance Metrics
- 17:27Show Estimated Plan
- 19:36Index Analysis
- 26:49Missing Index Recommendations
- 27:45Key Lookups
- 31:00Live Query Profile
- 34:12Live Query Demo
- 37:51Diagnostic Workflow
- 42:33Plan Diagram
- 49:49Conclusion
related talks
52mUnderstanding PostgreSQL Query Plans (aka EXPLAIN)
51mHere’s the execution plan … now what?
26mBe Good Friends with Query Planner
01h 00m7 Tips to Performance Tuning, Optimization, and Everything
23mBest Practices for Tuning Slow Postgres Queries
44mImproving Performance with Intelligent Query Processing
31mpg_stat_advisor: Optimizing PostgreSQL Planner with Insights
47mDebugging active queries...