Optimize find_best_temp_scaler for performance #1075
+10
−7
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.
Summary
This PR partially addresses #862
[ ✏️ Write your summary here. ]
I was profiling get_label_quality_multiannotator and it seems that find_best_temp_scaler took a long time when calibrate_probs was True. Almost all of the time was spent running compute_soft_cross_entropy. The idea is to skip the value_counts function (which calls np.unique) and instead rely on less expensive numpy operations as much as possible.
For memory I used the memory-profiler library. The code I used for benchmarking is copied below. In addition I sorted the imports in the modified files.
Code Setup
Current version
This PR
Testing
References
Reviewer Notes