performance-concurrency-advisor

Analyze performance and concurrency bottlenecks in Kotlin and Spring services.

4|Updated Jun 10, 2026
One-click install
npx skills add https://github.com/mymx2/foreman --skill performance-concurrency-advisor-mymx2
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: performance-concurrency-advisor
Source: https://github.com/mymx2/foreman/tree/main/.qoder/skills.collected/skills/performance-concurrency-advisor
Command: npx skills add https://github.com/mymx2/foreman --skill performance-concurrency-advisor-mymx2

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill resolves complex performance issues in Kotlin and Spring services by identifying the root cause of latency, throughput, and concurrency bottlenecks using evidence-based analysis.

Core Features & Use Cases

  • Evidence-Driven Diagnosis: Analyzes metrics, traces, SQL explain plans, and thread dumps to pinpoint constraints.
  • Concurrency Optimization: Provides expert guidance on thread pool tuning, reactive flow blocking, and lock contention.
  • Use Case: When a production service experiences intermittent latency spikes, use this skill to correlate thread pool saturation with database query performance to determine if the issue is I/O-bound or CPU-bound.

Quick Start

Use the performance-concurrency-advisor skill to analyze the provided thread dump and latency metrics to identify the root cause of the current service slowdown.

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 latency spikes and thread pool saturation in Spring services?

Diagnose latency spikes in Spring services by correlating thread pool saturation with database query performance using evidence from metrics and thread dumps. This determines whether bottlenecks are I/O-bound or CPU-bound for targeted optimization.

What is the best way to identify coroutine blocking in Kotlin applications?

Identify coroutine blocking in Kotlin by analyzing thread dumps and system signals to detect reactive flow blocking and lock contention. This evidence-driven approach pinpoints exact concurrency constraints causing throughput degradation.

How do I analyze database contention and slow endpoints using traces and metrics?

Analyze database contention and slow endpoints by evaluating SQL explain plans, distributed traces, and latency metrics together. This systematic evaluation reveals whether transactional scopes or query performance drive the bottleneck.

Can I use this approach to tune thread pools and event loops for high-throughput Kotlin services?

Yes, you can tune thread pools and event loops for high-throughput Kotlin services by systematically evaluating concurrency behavior against real system signals. This enables recommending high-leverage architectural changes for pool saturation.

When should I not use evidence-based concurrency analysis for performance bottlenecks?

Avoid evidence-based concurrency analysis when you lack accessible metrics, traces, or thread dumps, as this method requires real system signals to pinpoint constraints and recommend architectural changes.