⚡️ Speed up function _get_cartesian_label
by 122%
#125
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.
📄 122% (1.22x) speedup for
_get_cartesian_label
inplotly/_subplots.py
⏱️ Runtime :
1.52 milliseconds
→684 microseconds
(best of358
runs)📝 Explanation and details
Here’s the optimized version. Since this function does nothing heavy (just formatting a string in a simple controlled way), there isn’t much room for speedup. But Python’s f-strings are faster than
str.format
for this case, so we will use them for a micro-optimization.All comments are preserved. No functions or signatures changed.
This is the fastest way to express this logic in Python 3.6+ (including 3.11) without altering API or output.
✅ Correctness verification report:
🌀 Generated Regression Tests Details
To edit these changes
git checkout codeflash/optimize-_get_cartesian_label-mb2hhgp4
and push.