Add PyInstrument Profiling #9083
Open
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
Check out this pull request on See visual diffs & provide feedback on Jupyter Notebooks. Powered by ReviewNB |
|
@rasswanth-s what is the state of this PR? do we need it this week's release? |
|
@yashgorana , we do not need it for this week's release, but this is a useful feature for profiling our stack. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
The PR aims to add pyinstrument profiling support to in-memory workers.
The profiling functionality can be useful for
This can be triggered as simply by enabling a flag in orchestra
profile=TrueFor K8s tracing, we could do once OTel PR is merged.
Affected Dependencies
List any dependencies that are required for this change.
How has this been tested?
Add an example notebook for the same
Checklist