Skip to content

Conversation

@fridim
Copy link
Contributor

@fridim fridim commented Sep 11, 2025

  • use by changing the value of ENABLE_PROFILING env variable

  • Use signal to stop / start the profiler too

 # Start profiling
 oc exec <pod-name> -- kill -USR1 1

 # Stop profiling
 oc exec <pod-name> -- kill -USR2 1

 # Get results
 oc cp <pod-name>:/tmp/poolboy_profile.prof ./poolboy_profile.prof
 oc cp <pod-name>:/tmp/poolboy_profile_stats.txt ./poolboy_profile_stats.txt Use signal to stop / start the profiler too

- use by changing the value of ENABLE_PROFILING env variable

- Use signal to stop / start the profiler too
 # Find the operator PID
 kubectl exec <pod-name> -- pgrep -f "python.*operator"

 # Start profiling
 kubectl exec <pod-name> -- kill -USR1 <pid>

 # Stop profiling
 kubectl exec <pod-name> -- kill -USR2 <pid>

 # Get results
 kubectl cp <pod-name>:/tmp/poolboy_profile.prof ./poolboy_profile.prof
 kubectl cp <pod-name>:/tmp/poolboy_profile_stats.txt ./poolboy_profile_stats.txt Use signal to stop / start the profiler too
@jkupferer jkupferer closed this Oct 3, 2025
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

Successfully merging this pull request may close these issues.

2 participants