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

Perf: consider splitting jobs table into three tables - those with queues, those without, perma-failed #481

Open
benjie opened this issue Jul 1, 2024 · 0 comments
Open

Perf: consider splitting jobs table into three tables - those with queues, those without, perma-failed #481

benjie opened this issue Jul 1, 2024 · 0 comments

Comments

@benjie
Copy link
Member

benjie commented Jul 1, 2024

Maybe round-robin between the two tables when fetching jobs.

Doing this would make the queries easier to execute for the database, but would also reduce our accuracy around priority/runAt ordering.
@benjie benjie changed the title Perf: consider splitting jobs table into two tables - those with queues and those without. Perf: consider splitting jobs table into three tables - those with queues, those without, perma-failed Jul 1, 2024
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
@benjie