perf(workers): expedite user-facing and latency-critical WorkManager … - #6506
Merged
Conversation
…jobs Mark standalone OneTimeWorkRequests as expedited where completion time is bounded and either the user is waiting on it (delete/leave conversation, add participants, save/share/download a file, remove account) or it's notification-latency-sensitive (push/call notifications, post-push chat catch-up). Left non-expedited: chained/periodic requests (unsupported by WorkManager), long-running uploads not promoted to a foreground service, and pure background bookkeeping with no user-facing wait. Assisted-by: Claude Sonnet 5 <noreply@anthropic.com> Signed-off-by: Marcel Hibbe <dev@mhibbe.de>
Contributor
|
APK file: https://github.com/nextcloud/talk-android/actions/runs/32157657266/artifacts/9336828053 |
rapterjet2004
approved these changes
Aug 19, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
…jobs
Mark standalone OneTimeWorkRequests as expedited where completion time is bounded and either the user is waiting on it (delete/leave conversation, add participants, save/share/download a file, remove account) or it's notification-latency-sensitive (push/call notifications, post-push chat catch-up).
Left non-expedited: chained/periodic requests (unsupported by WorkManager), long-running uploads not promoted to a foreground service, and pure background bookkeeping with no user-facing wait.
Assisted-by: Claude Sonnet 5 noreply@anthropic.com
🏁 Checklist
/backport to stable-xx.x🤖 AI (if applicable)