Arthas Cpu High
- 3 installs
- 37.5k repo stars
- Updated July 24, 2026
- alibaba/arthas
arthas-cpu-high is a Claude skill that troubleshoots JVM/application CPU spikes using Arthas thread and profiling commands.
About
arthas-cpu-high is a Claude skill for troubleshooting JVM or application CPU spikes with Alibaba Arthas. A developer uses it when a machine's CPU is high or responses slow down. It walks from a low-risk dashboard overview to locating the busiest threads with thread topN, then narrows to the hot method or code path with stack, trace, or watch, and ends with a diagnostic conclusion.
- Step-by-step Arthas playbook for troubleshooting JVM/application CPU spikes
- Uses dashboard for an overview, then thread topN to find the busiest threads and stacks
- Narrows from busy thread to hot method via stack/trace/watch with execution limits
Arthas Cpu High by the numbers
- 3 all-time installs (skills.sh)
- Ranked #458 of 596 Debugging skills by installs in the Skillselion catalog
- Data as of Aug 5, 2026 (Skillselion catalog sync)
arthas-cpu-high capabilities & compatibility
Free; open-source Arthas tooling, no API keys.
- Capabilities
- cpu profiling · thread analysis · jvm diagnostics
- Use cases
- debugging
- Pricing
- Free
What arthas-cpu-high says it does
排查 JVM / 应用 CPU 飙高（线程定位 + 代码路径分析）
适用场景：机器 CPU 飙高、应用响应变慢、负载异常升高。
npx skills add https://github.com/alibaba/arthas --skill arthas-cpu-highAdd your badge
Show developers this skill is listed on Skillselion. Paste this into your README.
| Installs | 3 |
|---|---|
| repo stars | ★ 37.5k |
| Last updated | July 24, 2026 |
| Repository | alibaba/arthas ↗ |
What it does
Troubleshoot JVM or application CPU spikes with Arthas by locating the busiest threads and narrowing to the hot code path.
Who is it for?
Finding which thread and method cause a JVM CPU spike in production
Skip if: Non-JVM CPU issues or offline profiling
When should I use this skill?
A machine's CPU is high, responses slow down, or load spikes on a Java app
What you get
The busiest threads and the hot method or code path are identified with a diagnostic conclusion.
- A CPU-spike diagnosis with dashboard summary and topN thread stacks
By the numbers
- 4-step CPU-spike diagnostic workflow
Files
JVM CPU 飙高排查指南（Arthas）
适用场景：机器 CPU 飙高、应用响应变慢、负载异常升高。
原则：先用低风险工具定位「哪个线程在忙」，再逐步缩小到「哪个方法/代码路径」。
1) 先确认当前 JVM 整体状态（低风险）
- 使用
dashboard查看 CPU/线程/GC 概况（建议设置有限次数）： - 关注：CPU、线程数、GC 次数/耗时是否异常。
2) 定位最忙线程（关键步骤）
- 使用
thread找出最忙的前 N 个线程并打印堆栈： - 例如：
topN=3或topN=5 - 记录每个热点线程的
threadId与堆栈关键方法名（可用take_notes记录证据）。
判断方向：
- 如果堆栈显示在
java.util.regex、JSON 序列化、日志格式化等：可能是 CPU 密集计算。 - 如果堆栈显示在锁竞争：继续看是否有大量
BLOCKED，并考虑用thread(blocking=true)找出阻塞源头线程。
3) 进一步确认热点方法的调用路径（按需、有限制）
当热点线程堆栈指向某个「可疑方法」时：
- 优先使用
stack/trace针对该方法做路径确认（避免宽泛匹配）。 - 如果需要观测入参/返回值，再考虑
watch或tt，并设置合理的执行次数与超时，避免对线上造成压力。
4) 输出诊断结论
报告至少包含：
- 现象与证据：dashboard 摘要 + topN 线程堆栈关键片段
- 初步结论：CPU 主要消耗在什么类型的逻辑（计算/锁/GC/日志等）
- 下一步：建议进一步 trace/watch 的目标方法（给出类名+方法名的精确范围），或建议用户提供主包名/关键接口信息以继续收敛
Related skills
Azure DiagnosticsSystematically diagnose and resolve production issues on Microsoft Azure using official Microsoft guidance.495k1.3kAzure MessagingQuickly diagnose and fix connection, authentication, and message-processing failures when using Azure Event Hubs or Service Bus SDKs.483k1.3k
Diagnosing BugsGet a systematic, step-by-step process that surfaces the real root cause instead of guessing at bugs.291k200k
Use My BrowserWhen their agent task requires access to the live browser session, rendered DOM state, authenticated dashboards, localhost apps, or DevTools-selected elements instea269k71
Systematic DebuggingFollow a repeatable four-phase process that forces root-cause discovery before any code changes.210k265k
Safe DebugGet conservative, non-destructive diagnosis of deep learning and agent errors before any code changes are made.185k512FAQ
What is the first step?
Run the low-risk dashboard command to check CPU, thread count, and GC before doing anything invasive.
How do you find the hot thread?
Use thread with topN (for example topN=3 or 5) to print the busiest threads and their stacks, then narrow with stack/trace/watch.