Address performance regression in GQL subscriptions when using productBlockInstances #922
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.
The new SubscriptionModel querying from 3.2.0 turns out to have some adverse effects on the performance of the
subscriptionsGQL query, specifically when using theproductBlockInstancesfield. This particularly affects theSubscriptionDropdownOptionsquery.This PR mitigates this partially by:
productBlockInstances { ... }contains fieldinUseByRelationsModelCacheExtensionto reuse loaded subscription models throughout each GQL query operationWhich, at least for the
SubscriptionDropdownOptionsquery, reduces the execution time by 2/3rd.Bumps version to 3.2.2
Related orchestrator-ui-library PR: workfloworchestrator/orchestrator-ui-library#1872