Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

async-profiler can't find process by name when CPU is overloaded #854

Closed
gladko opened this issue Nov 30, 2023 · 3 comments
Closed

async-profiler can't find process by name when CPU is overloaded #854

gladko opened this issue Nov 30, 2023 · 3 comments

Comments

@gladko
Copy link

gladko commented Nov 30, 2023

trying to profile same simplest app as described in #852 but this time CPU burning activity is executed in ~15 threads and consumes all CPU.

Prerequisite: overloaded CPU

Processes: 687 total, 66 running, 621 sleeping, 4060 threads                                                                                                                                      15:25:11
Load Avg: 139.59, 158.15, 129.44  CPU usage: 96.46% user, 3.44% sys, 0.9% idle   SharedLibs: 665M resident, 131M data, 271M linkedit. MemRegions: 654554 total, 15G resident, 436M private, 4449M shared.
PhysMem: 31G used (2317M wired, 2103M compressor), 333M unused. VM: 312T vsize, 4285M framework vsize, 0(0) swapins, 0(0) swapouts. Networks: packets: 13379683/6160M in, 11675764/2524M out.
Disks: 3525473/84G read, 6985946/102G written.

PID    COMMAND      %CPU      TIME     #TH    #WQ   #PORTS MEM    PURG   CMPRS  PGRP  PPID  STATE    BOOSTS             %CPU_ME %CPU_OTHRS UID  FAULTS    COW       MSGSENT    MSGRECV    SYSBSD
36742  java         923.9     07:58:52 47/18  1     178    199M-  0B     0B     36742 83229 running  *0[1]              0.00000 0.00000    502  111094+   194       4550459+   2274675+   2094248+
8

S2R

  1. run jps to see running JVM
% jps                               
...
36742 PerfTestManager
  1. profiling
% profiler.sh -d 300 PerfTestManager
No Java process 'PerfTestManager' could be found!
Usage: /Users/vladimirkozak/workspace/tools/async-profiler-2.9-macos/profiler.sh [action] [options] <pid>
Actions:
  start             start profiling and return immediately
 ...
  1. run jps to see running JVM again and check if target process is still alive
% jps
...
36742 PerfTestManager
@apangin
Copy link
Collaborator

apangin commented Nov 30, 2023

Can you try with async-profiler 3.0-ea or with an up-to-date version from master?
It has major changes in the launcher, including the way how the target process is discovered.

@gladko
Copy link
Author

gladko commented Dec 1, 2023

can't reproduce it on master async-profiler

@gladko gladko closed this as completed Dec 1, 2023
@apangin
Copy link
Collaborator

apangin commented Dec 1, 2023

Thanks for confirming it works with the latest async-profiler.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants