performance-concurrency-advisor

Diagnose concurrency bottlenecks in Kotlin Spring services using metrics, traces, and SQL plans.

14|1|Updated Mar 6, 2026
One-click install
npx skills add https://github.com/kbrgnj/kotlin-backend-agent-skills --skill performance-concurrency-advisor-kbrgnj
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: performance-concurrency-advisor
Source: https://github.com/kbrgnj/kotlin-backend-agent-skills/tree/main/.agents/skills/performance-concurrency-advisor
Command: npx skills add https://github.com/kbrgnj/kotlin-backend-agent-skills --skill performance-concurrency-advisor-kbrgnj

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Analyze and improve performance, throughput, latency, and concurrency behavior in Kotlin + Spring services using real evidence from metrics, traces, SQL, thread or heap signals, and code paths. Use when endpoints are slow, pools saturate, coroutines or reactive flows block unexpectedly, N+1 or contention appears, or caching and parallelism decisions need precise, non-generic guidance.

Core Features & Use Cases

  • Evidence-driven bottleneck analysis across database, thread pools, event loops, and caches.
  • Layered diagnosis: queries, pools, I/O latency, serialization, and locking, with concrete, actionable recommendations.
  • End-to-end improvement plans that minimize risk while maximizing observable gains in latency and throughput.

Quick Start

Analyze a Kotlin Spring service to identify the bottleneck and propose a minimal high-impact fix.

Frequently Asked Questions about performance-concurrency-advisor

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

FAQPage Schema
How do I diagnose concurrency bottlenecks in a Kotlin Spring service?

Diagnose concurrency bottlenecks by analyzing latency metrics, traces, SQL plans, connection pool metrics, and thread dumps. This identifies the true constraint causing slow endpoints or pool saturation in Kotlin Spring services to justify a minimal high-impact fix.

Why are my Spring reactive coroutines blocking unexpectedly?

Reactive coroutines block unexpectedly when I/O latency, thread pool contention, or database locking occurs. Evidence-driven analysis of thread dumps and traces pinpoints the exact blocking code path across typical Spring stacks to resolve the constraint.

What's the best way to identify N+1 query issues using performance traces?

Identify N+1 query issues by evaluating SQL plans and traces alongside connection pool metrics. This layered diagnosis isolates query execution contention from other latency sources to provide actionable recommendations for database optimization.

Does this bottleneck analysis work with standard Spring connection pool metrics?

Bottleneck analysis works directly with standard Spring connection pool metrics, relying on real signals like latency data, SQL plans, and GC signals. It applies to typical Spring stacks experiencing pool saturation or contention without requiring custom instrumentation.

When do I need thread dumps and GC signals for latency analysis?

Thread dumps and GC signals are needed for latency analysis when coroutine blocking, thread contention, or memory pressure disrupts throughput. These signals reveal the true underlying constraint across I/O, pools, and caches beyond standard query performance metrics.