Repository navigation
Optimize datetime formatting code - #12626
Merged
Merged
Conversation
CodSpeed Performance ReportMerging #12626 will degrade performances by 10.44%Comparing Summary
Benchmarks breakdown
|
Contributor
Contributor
Author
|
Regression is unrelated volatility, all the gains are relevant and real 🎉 |
Viicos
approved these changes
Dec 16, 2025
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
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.
Change Summary
I was looking at cleaning up the
json_keymethods a bit (they create a lot of temporaryStringallocations). I found that these datetime methods needed particular work to clean up, so I'm pushing this first and separately:serializer.collect_str(s)instead ofserializer.serialize_str(&s.to_string())speedatetypes without having to go through Python attributes.Related issue number
N/A
Checklist