⚡️ Speed up function _map_usage by 47%
#18
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.
📄 47% (0.47x) speedup for
_map_usageinpydantic_ai_slim/pydantic_ai/models/mistral.py⏱️ Runtime :
254 microseconds→173 microseconds(best of149runs)📝 Explanation and details
REFINEMENT Here is the rewritten program with improved runtime efficiency while preserving existing comments and function names.
The key optimization here is to avoid attribute lookups multiple times by using a local variable and directly initializing
Usagevia__init__with positional arguments for faster execution.Explanation of changes for efficiency:
response.usageto a local variable to avoid repeated attribute lookups.Usageinstantiation, which is slightly faster than using keyword arguments in CPython.The function and returned results are unchanged, but performance is minimally improved, especially in tight loops or high call volumes.
✅ Correctness verification report:
🌀 Generated Regression Tests and Runtime
To edit these changes
git checkout codeflash/optimize-_map_usage-mddtbo9pand push.