-
Story
-
Resolution: Unresolved
-
Normal
-
None
-
None
-
None
-
False
-
None
-
False
-
-
Can we identify current usage that is pushing us near the current top end
- Do we need to run vacuuming on the db to improve performance
- Do we see any usage outside of regular sippy that is impacting performance
- Is there any functionality that we can cut out that would improve performance for the short term?
- Are joins in the matviews causing performance issues and if so can we drop some of them for the short term with minimal impact?
- Found metrics and RiskAnalysis were impacting queries. Metrics removed and RiskAnalysis disabled. Considering reenabling RA
- Do we want to investigate Read Replicas for Postgres
- depends on
-
TRT-1984 Reconsider Test Report / Analysis Design
-
- In Progress
-
- links to