tikv-fast-tune

Diagnose TiKV performance bottleneck root causes on TiDB Cloud clusters.

Updated Jun 3, 2026
One-click install
npx skills add https://github.com/alex-quan-001/nutshell-skills --skill tikv-fast-tune
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: tikv-fast-tune
Source: https://github.com/alex-quan-001/nutshell-skills/tree/main/skills/diagnosis/tikv-fast-tune
Command: npx skills add https://github.com/alex-quan-001/nutshell-skills --skill tikv-fast-tune

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Manually troubleshooting TiKV performance issues such as write/read latency spikes, throughput drops, and jitter on TiDB Cloud clusters is time-consuming, error-prone, and often leads to misdiagnosis of root causes across TiKV's complex internal layers.

Core Features & Use Cases

  • Deterministic Decision Tree: A machine-executable diagnostic flowchart that follows TiKV's layered architecture (from gRPC server down to disk) to systematically identify root causes, eliminating guesswork.
  • Version-Aware Metric Catalog: Includes exact PromQL queries for all relevant O11Y platform metrics, with automatic adaptation for TiKV 5.x/6.x vs 7.x+ metric name differences (e.g., raft-engine vs RaftDB metrics).
  • Use Case: For example, if your TiDB Cloud cluster experiences sudden write latency spikes, use this skill to run the decision tree to pinpoint if the root cause is disk fsync slowness, write stall, latch contention, PD scheduling disruption, or other layer-specific issues.

Quick Start

Use the tikv-fast-tune skill to diagnose the root cause of TiKV write or read performance issues on your TiDB Cloud cluster by following the built-in layer-aware decision tree.

Frequently Asked Questions about tikv-fast-tune

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I diagnose the root cause of TiKV write latency spikes on TiDB Cloud?

Diagnosing TiKV write latency spikes on TiDB Cloud requires a deterministic decision tree that uses Prometheus-compatible O11Y metrics to pinpoint layer-specific root causes like disk fsync slowness or latch contention, eliminating guesswork.

What is the best way to troubleshoot TiKV performance bottlenecks without guessing?

Troubleshooting TiKV performance bottlenecks is best done using a deterministic diagnostic flowchart that maps TiKV's layered architecture from gRPC server to disk, applying correlation-based spark detection to identify exact root causes across internal layers.

Does this TiKV performance diagnosis approach support different TiDB Cloud TiKV versions?

This TiKV performance diagnosis approach supports TiKV 5.x/6.x and 7.x+ versions on TiDB Cloud by automatically adapting metric names, including handling differences between raft-engine metrics and RaftDB metrics.

How do I identify if PD scheduling disruption causes TiKV throughput drops?

Identifying PD scheduling disruptions causing TiKV throughput drops involves running a layer-aware diagnostic workflow that queries O11Y metrics via PromQL to detect correlation-based sparks and isolate scheduling disruptions from write stalls.