diff --git a/PerformanceMonitor.Collectors/PlanCorrectionCollector.cs b/PerformanceMonitor.Collectors/PlanCorrectionCollector.cs index 6fbdd20408..05307c1fab 100644 --- a/PerformanceMonitor.Collectors/PlanCorrectionCollector.cs +++ b/PerformanceMonitor.Collectors/PlanCorrectionCollector.cs @@ -148,7 +148,7 @@ public sealed class Row /// /// /// Correcting the record, because it was wrong once and cost a round trip: #2760 removed both hints - /// on the theory that ~4,237ms of avg CPU seen on / was compile cost. That + /// on the theory that ~4,237ms of avg CPU seen on <host>/<database> was compile cost. That /// attribution was never verified — it was inferred from a CPU-heavy/low-read/low-row telemetry /// signature. The cost was the LIVE Query Store catalog-view joins that #2764 then replaced with /// staged temps. Removing RECOMPILE never addressed it; staging did. diff --git a/PerformanceMonitor.Collectors/QueryStoreOpenIntervalState.cs b/PerformanceMonitor.Collectors/QueryStoreOpenIntervalState.cs index 07d08116c4..89c7a9547b 100644 --- a/PerformanceMonitor.Collectors/QueryStoreOpenIntervalState.cs +++ b/PerformanceMonitor.Collectors/QueryStoreOpenIntervalState.cs @@ -65,7 +65,7 @@ public static class QueryStoreOpenIntervalState /// recorded rationale beats a knob nobody can reason about. /// /// Moved from 15 to 30 (#2759) because the #2312 yardstick it was tuned against — multi-53 at - /// ~50 s/run — stopped holding. Measured live on (2026-09-01, 3-hour + /// ~50 s/run — stopped holding. Measured live on <host> (2026-09-01, 3-hour /// window of collection_log): open-interval-inclusive runs cost 110–133 s each (2–2.5x the /// original yardstick), landing every 12–19 minutes — the 15-minute skip window was already firing as /// designed, spacing the expensive runs out, but each one had grown too large for that spacing to be