You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Pretty much all of my query plans, save for ModelBuild, require join operations on large tables. These joins will occur in such a way that a full index scan occurs and that is expensive. Even doing queries like looking for count of ModelTestRun that occurs before a given date causes a full index scan of ModelTestRun which has unacceptable performance.
The tables need to be optimized for the queries that can be run against them. Need to avoid full index scan here.
Need to take this one table at a time right now and work out from there.
Once I finish GCing the old rows and get the DB down to a reasonable size it should be possible to add the necessary new columns here to begin optimizing the queries.
The text was updated successfully, but these errors were encountered:
Pretty much all of my query plans, save for
ModelBuild
, require join operations on large tables. These joins will occur in such a way that a full index scan occurs and that is expensive. Even doing queries like looking for count ofModelTestRun
that occurs before a given date causes a full index scan ofModelTestRun
which has unacceptable performance.The tables need to be optimized for the queries that can be run against them. Need to avoid full index scan here.
Need to take this one table at a time right now and work out from there.
Once I finish GCing the old rows and get the DB down to a reasonable size it should be possible to add the necessary new columns here to begin optimizing the queries.
The text was updated successfully, but these errors were encountered: