Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Need to rethink the query plans #106

Open
jaredpar opened this issue Mar 30, 2021 · 0 comments
Open

Need to rethink the query plans #106

jaredpar opened this issue Mar 30, 2021 · 0 comments

Comments

@jaredpar
Copy link
Owner

jaredpar commented Mar 30, 2021

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant