Skip to content

Persist full job completion batches concurrently #1434

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

Draft
bgentry wants to merge 2 commits into
base: master
Choose a base branch
from
+632 −95
Draft

Persist full job completion batches concurrently #1434

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
8a8fd7c
add job completion concurrency capabilities
bgentry Oct 4, 2026
adba3de
parallelize full completion batches
bgentry Oct 4, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 4 additions & 0 deletions CHANGELOG.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -7,6 +7,10 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0

## [Unreleased]

### Changed

- When both the driver and pilot support it, which the PostgreSQL drivers do, the batch job completer now persists up to two full batches of job completions concurrently, improving completion throughput under heavy load. Results for the same job are still applied in order, but subscribers may receive completion events for different jobs in a different order than before, and the completer may briefly use one additional database connection. [PR #1434](https://github.com/riverqueue/river/pull/1434).

## [0.49.0] - 2026-10-05

⚠️ If using River Pro, make sure to upgrade it to at least River Pro v0.32.0 to get a compatible package.
Expand Down
Loading
Loading