Limit Karton analyses list to 10 elements, add pagination and optimize handling of object relationships #1095
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.
Your checklist for this pull request
What is the current behaviour?
Motivation is similar to #1023. When we are querying or uploading a very popular object with incrementally growing number of relationships and Karton analyses, all of these analyses are loaded by backend and returned which causes excessive use of resources and request timeouts.
In case of Karton analyses, Karton backend is additionally asked for status of each analysis which causes additional overhead. The result is usually worker killed with WORKER TIMEOUT.
What is the new behaviour?
older_thanparameter.Object.analysesandObject.parentsalso during creation/removal of the relationships. Right now we observe that WORKER TIMEOUT happens also when such "popular" object is uploaded.Test plan
API correctness should be already covered by automated tests. "Popular" object querying and upload was tested manually.
Closing issues
closes #1050