This repository has been archived by the owner on Nov 16, 2023. It is now read-only.
OR_4243_Labelstudio_Change_prediction_upload_algorithm #15
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.
PR fulfills these requirements
[fix|feat|ci|chore|doc]: TICKET-ID: Short description of change made
ex.fix: DEV-XXXX: Removed inconsistent code usage causing intermittent errors
Change has impacts in these area(s)
(check all that apply)
Describe the reason for change
We figured out that 90% of the time during the prediction generation is spend during prediction upload to the label studio backend:
this is caused by posting each prediction individually to the backend
this is probably causing a separate update to the database as well
Please rewrite the algorithm to use bulk_create to significantly increase the data download speed.
What does this fix?
What is the new behavior?
Now on my test dataset with 1300 images, predictions are saved to the database in 7 seconds instead of 1 minute 30 seconds. And the same annotation count uploads in ~15 seconds instead of ~ 2 minute.
Does this PR introduce a breaking change?
(check only one)