Fix XE ring buffer query timeouts on large buffers#38
Merged
erikdarlingdata merged 1 commit intodevfrom Feb 15, 2026
Merged
Conversation
Materialize the ring buffer XML into a table variable before shredding with CROSS APPLY .nodes(). The inline subquery pattern forced SQL Server to repeatedly parse the full 4MB+ XML blob, causing 2+ minute execution times and 30-second CommandTimeout failures during sustained load. Applied to all 4 XE ring buffer queries: - Deadlock collection (on-prem + Azure SQL DB) - Blocked process report collection (on-prem + Azure SQL DB) Performance: ~2:44 → ~0.46s (~350x improvement). Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Fixes #37 — XE ring buffer queries for deadlock and blocked process collection timeout when the buffer is large (4MB+ during sustained load testing).
CROSS APPLY .nodes()Test plan
dotnet build Lite/PerformanceMonitorLite.csproj -c Debug— builds clean🤖 Generated with Claude Code