⚡️ Speed up function _customize_output_object
by 27%
#25
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.
📄 27% (0.27x) speedup for
_customize_output_object
inpydantic_ai_slim/pydantic_ai/models/__init__.py
⏱️ Runtime :
48.2 microseconds
→38.1 microseconds
(best of249
runs)📝 Explanation and details
REFINEMENT Here is an optimized version of your program. The main optimization is to avoid unnecessary use of
dataclasses.replace
if thejson_schema
is not actually changed, which can be a hot path if this function is called many times. The local variable nameson_schema
is fixed tojson_schema
to avoid confusion. The code also minimizes attribute lookups.Notes:
type(o)(**{**o.__dict__, "json_schema": new_schema})
avoids the overhead ofdataclasses.replace
and is ~2x faster for single-field changes.Let me know if you'd like further profiling or optimization!
✅ Correctness verification report:
🌀 Generated Regression Tests and Runtime
To edit these changes
git checkout codeflash/optimize-_customize_output_object-mdetm4ay
and push.