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.
Using materialized views will create a copy of the data in a preprocessed and stored way for postgresql to do more efficient queries against.
Some quick numbers from my local setup, non-scientific, using NAV data:
MonthlyCostForTeam
236.52ms
514μs
2.288s
DailyEnvCostForTeam
16.9ms
14.96ms
ResourceUtilizationRangeForTeam
254.88ms
462μs
1.439s
QI Avg: Average execution time as reported by Query Insights for live NAV environment
Pros
Cons
Some more testing needs to be done to verify the usefulness of each materialized view.
Need to create trigger when the source changes.