⚡️ Speed up method RedisDBConfig.validate_extra_fields by 63%
#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.
📄 63% (0.63x) speedup for
RedisDBConfig.validate_extra_fieldsinmem0/configs/vector_stores/redis.py⏱️ Runtime :
42.4 microseconds→26.1 microseconds(best of61runs)📝 Explanation and details
The optimization applies field caching to eliminate redundant computation in the validation method.
Key changes:
set(cls.model_fields.keys())on every validation, the code now caches the result ascls._allowed_fieldsusingfrozensetfor O(1) membership testing.Why this is faster:
cls.model_fields.keys(), which involves dictionary key extraction and set construction.frozensetinstead ofsetprovides faster membership testing for the set difference operation (input_fields - allowed_fields).Performance gains by test type:
The 62% overall speedup demonstrates significant performance improvement for a common validation pattern, especially valuable if this validator runs frequently during model instantiation.
✅ Correctness verification report:
🌀 Generated Regression Tests and Runtime
To edit these changes
git checkout codeflash/optimize-RedisDBConfig.validate_extra_fields-mhlco6j1and push.