Moved endpoint execution outside of get_request_handler for profiling#1027
Merged
Conversation
Codecov Report
@@ Coverage Diff @@
## master #1027 +/- ##
======================================
Coverage 100% 100%
======================================
Files 294 297 +3
Lines 7732 7815 +83
======================================
+ Hits 7732 7815 +83
Continue to review full report at Codecov.
|
Member
|
Great! I updated it a bit to re-use the precomputed Thanks for your contribution! 🚀 🎉 🍰 |
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
At the reccomendation of @tiangolo in #701 (comment), I have moved the endpoint execution section from
routing.get_request_handler.<locals>.appto a separate function (currently named_run_endpoint) in order to facilitate profiling. Internal functions and callable object properties make it difficult for profilers to identify the function object being called, and since each request is only associated to one endpoint (not counting dependencies), this makes possible to simply profile "the endpoit that was used" for any given request.