Skip to content
cccskills
FreePublished on GitHub

arthas-cpu-high

Investigate high CPU usage in Java applications with Arthas. Identify busy threads, inspect method call paths, and produce an evidence-based diagnosis with specific methods to examine next.

OriginalShow the original description

排查 JVM / 应用 CPU 飙高(线程定位 + 代码路径分析)

See how to install

Good for

  • Investigating sudden CPU spikes in Java applications
  • Finding busy threads behind slow application responses
  • Narrowing down methods for further tracing
  • Preparing a diagnosis with supporting evidence

Files included (1)

  • SKILL.md1.8 KB

SKILL.md (original)

Review the instructions the agent will receive before you install.

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 的目标方法(给出类名+方法名的精确范围),或建议用户提供主包名/关键接口信息以继续收敛

Reviews

No reviews yet. Tell others what you thought.

Comments

No login needed. Share how it worked for you, ask a question, or note where it did not run.

No comments yet. Be the first to write one.

Comments are published right away. Do not include personal information such as email addresses or phone numbers. Up to 2 URLs.

0 / 1,000 characters

This form is protected by reCAPTCHA, and the Google Privacy Policy and Terms of Service apply.

More skills from this repository

arthas

FreeSummary

Diagnose running Java applications with Arthas. Follow guides for high CPU usage, retrieving EagleEye request tracking IDs, and inspecting Spring configuration and managed objects, then summarize evidence and next steps.

  • Diagnosing high CPU usage in Java applications
  • Retrieving EagleEye traceId values to find related logs
  • Checking Spring configuration values and their sources
alibaba/arthas37.6KUpdated Oct 9, 2026

Retrieve an EagleEye traceId, an identifier linking a request across logs, using Arthas without changing application code. Observe request-handling methods, capture parameters when needed, and inspect method calls and timings to investigate problems.

  • Retrieving a request's traceId without code changes
  • Matching request parameters with related logs
  • Inspecting method calls and execution times
alibaba/arthas37.6KUpdated Oct 9, 2026

Investigate Spring configuration and Beans, the objects Spring manages, using Arthas. Check configuration sources, find registered objects by name or type, and inspect registration details while prioritizing read-only queries.

  • Checking configuration values and where they came from
  • Investigating a Bean that appears to be missing
  • Finding candidate implementations for dependency injection
alibaba/arthas37.6KUpdated Oct 9, 2026

See all skills by alibaba

Report a problem with this skill