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

Profiling process and all calls happening in it #47

Open
hauleth opened this issue Jun 26, 2024 · 2 comments
Open

Profiling process and all calls happening in it #47

hauleth opened this issue Jun 26, 2024 · 2 comments

Comments

@hauleth
Copy link

hauleth commented Jun 26, 2024

I am working on profiling Ranch protocol handler which is implemented as gen_statem. Currently I am tracing all handle_event/4 function calls, but that results in a lot of separate traces and it is hard to see overall picture. Would it be possible to trace single process (ideally running it from source code)? It would make profiling such code way easier than current workaround (I have tried monitoring enter_loop which I use, but that never produced any output).

@Stratus3D
Copy link
Owner

So you want a limited number of call traces, but only for a specific pid?

@hauleth
Copy link
Author

hauleth commented Jun 29, 2024

I want to listen for all calls within given PID. Alternatively (in this particular case) if there would be a possibility for time limit (like in #48) then I could listen on enter_loop (which never exits) and then limit it by elapsed time.

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