Add project and domain filters in order to hit DB index #patch #891
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.
TL;DR
This addresses the issue described in flyteorg/flyte#6428 where DB queries don't use the indexes on the
workflows
,tasks
andlanuchplans
table. This slows down the UI significantly and spikes the CPU usage of the database server.Type
Are all requirements met?
Complete description
The index in the database is over the three columns
(name, project, domain)
- not JUSTname
. Therefore when filtering, we need to pass all these values in order to leverage the index.Tracking Issue
fixes flyteorg/flyte#6428