⚡️ Speed up function _should_show_onboarding_reminder by 253%
#5
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.
📄 253% (2.53x) speedup for
_should_show_onboarding_reminderinpdd/cli.py⏱️ Runtime :
1.33 milliseconds→378 microseconds(best of124runs)📝 Explanation and details
The optimized code achieves a 253% speedup through two key optimizations:
1. Generator Expression with
next()in_first_pending_command()next((arg for arg in ctx.protected_args if not arg.startswith("-")), None)2. LRU Cache on
_api_env_exists()@lru_cache(maxsize=1)to cache the filesystem check result~/.pdd/api-envfile rarely changes during a session, but the function is called repeatedly_should_show_onboarding_reminder()exists()calls which are expensive system operationsPerformance Impact by Test Case:
The optimizations are particularly effective for the common onboarding check scenario where multiple filesystem and argument parsing operations occur in sequence.
✅ Correctness verification report:
🌀 Generated Regression Tests and Runtime
To edit these changes
git checkout codeflash/optimize-_should_show_onboarding_reminder-mgmoginfand push.