waits-latches-spinlocks-workshop
Skill1 starsChanged 12 days agoMITView on GitHub
Guide the numbered Inside Waits, Latches, and Spinlocks workshop: WinDbg basics, blocking, scheduler yield, preemptive waits, threadpool exhaustion, log governance, latches, and spinlocks. Use for examples/insidewaitslatchesspinlocks_workshop.
In this repository20 other files it gives its agents.
- nvidianimSkill
- zavahospitalSkill
- shift-handoffSkill
- adventureworksSkill
- auto-index-compactionSkill
- azure-sql-aiSkill
- debugging-sqlSkill
- inside-transaction-logSkill
- polybaseSkill
- powerapps-sqlSkill
- secure-scalable-db-appSkill
- sql-by-exampleSkill
- sql-linuxSkill
- sqlserver2022Skill
- sqlserver2025Skill
- sql-versioning-appsSkill
- sql-versioningSkill
- tempdb-growthSkill
- waits-latches-spinlocksSkill
- wardgeneralSkill
The file
We split this skill into the rules it gives an agent
6 rules. About 0 are common, 5 are distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈5
Distinctive · estimate
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 10
Read the module map. Select a numbered module and read its own README and scripts.
- Distinctive: line 13
Verify the isolated Windows SQL Server build, WinDbg/symbol setup, SQL tools, and required stress driver.
- Distinctive: line 20
Use separate workload/diagnostic sessions and prepare DAC access before threadpool experiments that may block ordinary connections.
- Distinctive: line 22
Run only the approved module sequence.
- Distinctive: line 25
Stop only the specific lab process IDs, close transactions, detach safely, restore configuration, and follow module cleanup before …
- Distinctive: line 28
Never run these reproductions in production.
≈ “Common” is an estimate: at least 1 in 5 of the 372,429 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Waits, latches, and spinlocks workshop
Procedure
- Read the module map.
Select a numbered module and read its own README and scripts. This is
separate from the shorter
insidewaitslatchesspinlockscollection. - Verify the isolated Windows SQL Server build, WinDbg/symbol setup, SQL tools, and required stress driver. Start with module 0 when debugger prerequisites or safe attach/detach procedures are unfamiliar.
- Review targets, authentication, startup flags, affinity, Resource Governor, worker limits, and cleanup. Obtain explicit approval before process attachment, instance changes, server restarts, or heavy/failure workloads.
- Capture baseline request/wait, CPU, latch/spinlock, or log observations. Use separate workload/diagnostic sessions and prepare DAC access before threadpool experiments that may block ordinary connections.
- Run only the approved module sequence. Resolve internal symbols and type IDs against the actual build; distinguish waits and cumulative counts from evidence of the reproduced bottleneck. Captured driver files are historical.
- Stop only the specific lab process IDs, close transactions, detach safely, restore configuration, and follow module cleanup before continuing.
Never run these reproductions in production. Keep dumps/logs private until reviewed and follow secret checks.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

