⚡️ Speed up function coco_categories_to_classes
by 22%
#58
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.
📄 22% (0.22x) speedup for
coco_categories_to_classes
insupervision/dataset/formats/coco.py
⏱️ Runtime :
259 microseconds
→212 microseconds
(best of559
runs)📝 Explanation and details
To optimize the runtime of this function, we can avoid the overhead of the lambda function by using the
itemgetter
from theoperator
module, which is generally faster for this kind of key extraction. Let's rewrite the function accordingly.This minor change leverages the
itemgetter
for sorting, which should improve performance. The rest of the logic remains the same, providing the same return values for the given input.✅ Correctness verification report:
⚙️ Existing Unit Tests Details
🌀 Generated Regression Tests Details