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.

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

Deprioritize background jobs over user-initiated actions #657

Closed
eloquence opened this issue Dec 10, 2019 · 3 comments · Fixed by #708
Closed

Deprioritize background jobs over user-initiated actions #657

eloquence opened this issue Dec 10, 2019 · 3 comments · Fixed by #708
Assignees
Labels

Comments

@eloquence
Copy link
Member

To ensure the client is consistently responsive, we should always treat user-initiated actions (replies, starring, deletion, user-initiated sync) as higher priority than background operations (currently: automatic metadata syncs and jobs it adds to the queue).

Fully closing this issue is blocked on #655.

@eloquence
Copy link
Member Author

@sssoleileraaa
Copy link
Contributor

the only thing we shouldn't deprioritize is MetadataSyncJob but looks like @redshiftzero's WIP branch doesn't do that so this is fine

@eloquence
Copy link
Member Author

Added to milestone; IMO must-do for beta as part of the critical work to optimize responsiveness of the client. See #652 and #657 as well.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants