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

How do we know which heapshot/cpuprofile files relates to which PID w/o loading #1676

Open
smartmouse opened this issue Dec 8, 2015 · 4 comments
Labels

Comments

@smartmouse
Copy link

-rw-r--r-- 1 nodebot nodebot 189980672 Dec 7 21:48 minkelite.db
-rw-rw-r-- 1 nodebot nodebot 14081 Dec 7 21:01 profile.1.cpuprofile
-rw-rw-r-- 1 nodebot nodebot 12934 Dec 7 21:02 profile.2.cpuprofile
-rw-rw-r-- 1 nodebot nodebot 18905 Dec 7 21:02 profile.3.cpuprofile
-rw-rw-r-- 1 nodebot nodebot 63648 Dec 7 21:06 profile.4.cpuprofile
-rw-rw-r-- 1 nodebot nodebot 24319 Dec 7 21:06 profile.5.cpuprofile
-rw-rw-r-- 1 nodebot nodebot 45136 Dec 7 21:06 profile.6.cpuprofile
-rw-rw-r-- 1 nodebot nodebot 25678345 Dec 7 21:06 profile.7.heapsnapshot
-rw-rw-r-- 1 nodebot nodebot 25787072 Dec 7 21:07 profile.8.heapsnapshot
-rw-rw-r-- 1 nodebot nodebot 9214 Dec 7 17:47 start.log
-rw-rw-r-- 1 nodebot nodebot 90342 Dec 7 21:48 strong-pm.json

There are mulitple clusters/PID(process) running and we take diffetent heap and cpu profile on different PID process in ARC.

Is there a way to tell just which PID from the cpuprofile or heapsnapshot

@cgole
Copy link
Member

cgole commented Dec 10, 2015

@jtary when you run cpu profiling through Arc they show up with pid number in the left side bar which is good enough. These profiles also get saved in ~/.strong-pm but there they are saved as @smartmouse pointed out, without pid numbers. Can we keep them in sync and have the pid numbers in the profiles when we save them?

@cgole cgole added the bug label Dec 10, 2015
@jtary
Copy link
Contributor

jtary commented Dec 11, 2015

Would probably be fairly straight forward, but it's on the PM side. @sam-github would know better if there would be any particular issue with changing the naming scheme.

@sam-github
Copy link
Contributor

@smartmouse you are looking directly into strong-pm's internal DB... you can if you want, but its not intended to be user-readable. Use strong-arc to connect to strong-pm and browse the profiles.

FYI, the number is the profile ID, you can observe what app/pid/worker/etc. it is from by looking in explorer.

And, mea culpa, we don't have a CLI equivalent of the strong-arg profile browser... we should.

Anyhow, definitely not a bug, but a reasonable feature request to have a CLI way of browsing and accessing the profiles. Can you remove bug label and backlog this?

/cc @kraman

@sam-github
Copy link
Contributor

It should be backlogged against strong-pm in nodeops, not in arc.

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

No branches or pull requests

5 participants