メニュー
Use when demonstrating or tuning a sysbench + MySQL workload with sched-claw. Covers the demo launcher, direct throughput and latency metrics, and workload-specific scheduler implications.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
Use when sched-ext source has to be edited, then compiled, verifier-checked, and persisted with concrete artifacts. Covers build command hygiene, libbpf or verifier triage, and script-friendly artifact capture.
Use when baseline and candidate runs need to be executed and compared with reproducible artifacts instead of free-form notes. Covers repeated runs, metrics import, noise handling, and script-driven comparison instead of host-owned scoring.
Use when a tuning request needs to be turned into a durable workload contract before any sched-ext code is changed. Covers selectors, direct metrics, proxy metrics, guardrails, and saved contract hygiene.
Use when a sched-ext candidate is about to be activated through the privileged daemon. Covers rollout gates, daemon usage limits, rollback triggers, and how to keep deployment evidence attributable.
Use when collected scheduler evidence needs to be turned into explicit facts, inferences, unknowns, and candidate design implications. Covers repo helper scripts for uv-managed analysis environments, pandas or polars summaries, and matplotlib plots.
Use when scheduler-related performance evidence has to be collected reproducibly for a workload, target selector, or experiment phase. Covers low-overhead counters first, escalation to traces, and repo scripts that keep capture deterministic without baking a workflow into the host.
SOC 職業分類に基づく
| name | mysql-sysbench-tuning |
| description | Use when demonstrating or tuning a sysbench + MySQL workload with sched-claw. Covers the demo launcher, direct throughput and latency metrics, and workload-specific scheduler implications. |
| aliases | ["mysql-demo","sysbench-mysql-tuning"] |
| tags | ["sched-claw","mysql","sysbench","database","scheduler"] |
This is a workload profile, not a foundational workflow skill. It should supply workload-specific metrics, likely policy levers, and launcher details, then compose the generic contract, collection, analysis, policy, codegen, and rollout skills.
sched-workload-contractsched-perf-collectionsched-perf-analysissched-policy-mappingsched-ext-codegensched-ext-run-evaluationsched-ext-rollout-safetytransactions_per_sec:maximizequeries_per_sec:maximizep95_latency_ms:minimizeavg_latency_ms:minimizeapps/sched-claw/scripts/demos/mysql-sysbench-autotune.shapps/sched-claw/scripts/workloads/run-mysql-sysbench.shapps/sched-claw/scripts/docker/sysbench-runner.Dockerfilerun.log, prepare.log, and metrics.env.references/demo-contract.md