Perf: consider splitting jobs table into three tables - those with queues, those without, perma-failed
Open
- Dominant language
- TypeScript
- Stars
- 2.4k
- Forks
- 126
- Avg merge
- 2d 2h
- Merged PRs (30d)
- 9
Description
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.
Contributor guide
No contributing guide indexed for this repository
Assessment
This issue has not been assessed yet.