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.

Sign up for GitHub

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

Jump to bottom

/submissions/count query not optimal #5

Open
nonword opened this issue Jul 25, 2016 · 0 comments
Open

/submissions/count query not optimal #5

nonword opened this issue Jul 25, 2016 · 0 comments

Comments

@nonword
Copy link
Contributor

nonword commented Jul 25, 2016

Looks like the sql run at /submissions/count is a select count(*) around a sub-query with no LIMIT. I believe that query time will grow linearly with table size. Instead, db.makeSubmissionsQuery should maybe have a second param just_count that causes the sql returned to be a proper count(*) query.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@nonword