Skip to content

fix(profiling): Delay start of profiler thread #1901

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

Closed
wants to merge 1 commit into from

Conversation

Zylphrex
Copy link
Member

When using uWSGI with the master enabled, the profiler thread is started in the master process. However, when uWSGI forks the worker processes, the profiler thread will not be present in the worker process. This means that we never take any samples. To address this, we delay the start of the profiler thread until the first profile to guarantee it is started within the worker threads.

When using uWSGI with the master enabled, the profiler thread is started in the
master process. However, when uWSGI forks the worker processes, the profiler
thread will not be present in the worker process. This means that we never take
any samples. To address this, we delay the start of the profiler thread until
the first profile to guarantee it is started within the worker threads.
@Zylphrex
Copy link
Member Author

closing in favour of #1903

@Zylphrex Zylphrex closed this Feb 15, 2023
@antonpirker antonpirker deleted the txiao/fix/delay-start-of-profiler-thread branch January 9, 2025 10:04
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.

1 participant