I'm trying to debug the CPU usage on a production server. I have the agent running on the server and I connect via an SSH tunnel. I can sample the CPU usage, but I need to use tracing because sampling doesn't seem to show the cause of the high CPU usage.
When I turn on tracing, the application stops working. It is running, but it is unable to handle any requests by the users and the CPU usage of the application jumps close to 100%.
I've tried to run the application on an instance that has double CPU but the results are the same.
What am I doing wrong? How can I get CPU tracing working on a remote application via an SSH tunnel?
Cannot do CPU Profiling with Tracing on a remote application
-
- Posts: 1
- Joined: Tue Oct 31, 2017 12:09 pm
-
- Posts: 6172
- Joined: Wed Aug 11, 2004 8:37 am
Re: Cannot do CPU Profiling with Tracing on a remote applica
Perhaps CPU tracing overhead is too high in your particular case.
Could you please provide:
- the profiler agent log file from the remote machine: ~/.yjp/log/<session name>-<pid>.log
- a performance snapshot file (.snapshot) captured after you start CPU tracing
You may send this information to [email protected]
Could you please provide:
- the profiler agent log file from the remote machine: ~/.yjp/log/<session name>-<pid>.log
- a performance snapshot file (.snapshot) captured after you start CPU tracing
You may send this information to [email protected]