waits-latches-spinlocks
Skill1 starsChanged 12 days agoMITView on GitHub
Investigate SQL Server waits, scheduler yield, buffer latches, LOCK_HASH spinlocks, and Azure SQL log governance. Use when working with examples/insidewaitslatchesspinlocks and its debugwaits, latches, spinlocks, or loggovernance areas.
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-spinlocks-workshopSkill
- wardgeneralSkill
The file
We split this skill into the rules it gives an agent
5 rules. About 0 are common, 4 are distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈4
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
Use the collection map to choose the scenario.
- Distinctive: line 16
Use a disposable lab. Obtain approval before restarts, debugger attachment, Resource Governor changes, heavy traffic, bulk inserts, or …
- Distinctive: line 20
Run the approved workload in the intended sessions, then compare deltas and stacks rather than equating a cumulative wait count with the …
- Distinctive: line 24
Stop the specific lab processes, close transactions, detach the debugger, and follow the chosen cleanup while restoring prior settings.
- Distinctive: line 27
Do not run contention or failure 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
Procedure
- Use the collection map
to choose the scenario. Read its Markdown entry point and retained
readme.txtinstructions. - Confirm platform, SQL build/tier, instance, SQL tools, and the scenario's WinDbg/symbol or stress-driver dependencies. Review startup flags, authentication, local paths, and resource limits.
- Use a disposable lab. Obtain approval before restarts, debugger attachment, Resource Governor changes, heavy traffic, bulk inserts, or configuration changes. Supply credentials privately; do not reuse literal demo passwords.
- Capture baseline requests, wait/latch/spinlock counters, and CPU/log metrics. Run the approved workload in the intended sessions, then compare deltas and stacks rather than equating a cumulative wait count with the root cause.
- Resolve spinlock type IDs and internal symbols against the current build. Captured driver output is reference material, not proof of current behavior.
- Stop the specific lab processes, close transactions, detach the debugger, and follow the chosen cleanup while restoring prior settings.
Do not run contention or failure reproductions in production. Follow secret checks before publishing logs or scripts.
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.

