performance-concurrency-advisor

Diagnose Kotlin Spring service bottlenecks using metrics, traces, and system signals.

14|1|Updated Mar 6, 2026

Search Tags:#performance #metrics #concurrency #profiling #bottlenecks #kotlin #spring

Ready to run

npx skills add https://github.com/yalishevant/kotlin-backend-agent-skills --skill performance-concurrency-advisor-yalishevant

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: performance-concurrency-advisor
Source: https://github.com/yalishevant/kotlin-backend-agent-skills/tree/main/.agents/skills/performance-concurrency-advisor
Command: npx skills add https://github.com/yalishevant/kotlin-backend-agent-skills --skill performance-concurrency-advisor-yalishevant

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Analyze and improve performance, throughput, latency, and concurrency behavior in Kotlin plus 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 diagnosis across layers (database, connection pools, thread pools, event loops)
Guidance on targeted, measurable optimizations with minimal risk
Real-world use cases: slow endpoints, saturation, blocking in reactive or coroutine code, N+1 queries, cache invalidation churn

Quick Start

Use a focused performance review workflow on a Kotlin Spring service to locate the true bottleneck and propose minimal impactful changes.

Frequently Asked Questions about performance-concurrency-advisor

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

FAQPage Schema

How do I find the true bottleneck causing slow latency in a Kotlin Spring service?▼

To identify the bottleneck causing slow latency in a Kotlin Spring service, analyze real metrics, traces, SQL plans, and pool metrics to isolate the exact layer limiting performance. This evidence-driven approach locates the true bottleneck across databases, thread pools, or external calls.

Why are my Spring coroutines or reactive flows blocking unexpectedly under load?▼

Spring coroutines or reactive flows block unexpectedly under load when thread pools saturate or event loops get blocked by synchronous operations. Diagnosing this requires analyzing traces and system signals to isolate the blocking code path and propose a minimal high-impact change.

What metrics do I need to diagnose connection pool saturation and N+1 queries in Spring?▼

Diagnosing connection pool saturation and N+1 queries in Spring requires collecting latency percentiles, distributed traces, SQL execution plans, and pool utilization metrics. These signals reveal exactly where database contention occurs and guide targeted optimizations with clear tradeoffs.

Can I use this approach to fix cache invalidation churn and serialization bottlenecks in Spring?▼

Yes, you can use this approach to fix cache invalidation churn and serialization bottlenecks in Spring by analyzing real metrics and code paths. It evaluates caching and parallelism decisions to provide precise, non-generic guidance for measurable optimizations with minimal risk.

What is the best way to optimize Kotlin Spring throughput without introducing high-risk changes?▼

The best way to optimize Kotlin Spring throughput without high-risk changes is diagnosing bottlenecks with real evidence to propose the smallest high-impact change. This method evaluates precise tradeoffs across concurrency, database, and caching layers to ensure targeted, measurable optimizations.