feat: Improve triggers query performances #2256
Merged
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.
We used to query all triggers, in order to determine which konnectors accounts are connected, to adapt display on the homepage.
However, this query can be very time-consuming: it takes ~10s on an instance with 700+ triggers and ~2.2s on an instance with 150 triggers. This is due to the stack computing job information from each trigger.
As we do not need such information here, we force the generic
/data
route, rather than the specialized/jobs/triggers
route.With 150 triggers, we improve query time from ~2200ms to ~50ms.