Chain-trigger parsers, optimize XML collection, tune schedule#88
Merged
erikdarlingdata merged 1 commit intodevfrom Feb 17, 2026
Merged
Chain-trigger parsers, optimize XML collection, tune schedule#88erikdarlingdata merged 1 commit intodevfrom
erikdarlingdata merged 1 commit intodevfrom
Conversation
…e schedule (#86) - Blocked process and deadlock XML collectors now chain-trigger their parsers and analyzer immediately when rows are found, eliminating up to 15 min pipeline latency - Materialize XE ring buffer XML into table variable before shredding, avoiding repeated XML document validation (35s → 300ms under load) - Master collector passes @minutes_back = frequency * 2 instead of defaulting to 15 min lookback every cycle - Bump 18 cheap collectors to 1-min frequency, 4 medium to 2-min Tested on sql2022 under TPC-C workload: 79 deadlock events collected in 297ms (was 35s), chain triggers fire correctly, zero CHAIN_ERRORs. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
This was referenced Feb 17, 2026
Merged
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
Closes #86
CHAIN_ERRORlog entries — never fail the parent collector..value()/.query()call. Under TPC-C load: 35s → 297ms for 79 deadlock events.@minutes_back = frequency * 2instead of always defaulting to 15 minutes. At 1-min frequency this means looking back 2 minutes instead of 15 — the single biggest factor in the 100x speedup.Test plan
CHAIN_ERRORentries in collection_log🤖 Generated with Claude Code