Last-Rendered Image: refactor queue to be per job #99394
Labels
No Label
Good First Issue
Priority
High
Priority
Low
Priority
Normal
Status
Archived
Status
Confirmed
Status
Needs Info from Developers
Status
Needs Information from User
Status
Needs Triage
Status
Resolved
Type
Bug
Type
Design
Type
Job Type
Type
Known Issue
Type
Patch
Type
Report
Type
To Do
No Milestone
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: studio/flamenco#99394
Loading…
Reference in New Issue
Block a user
No description provided.
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
The "last rendered image" processing queue is currently a single, limited-size queue. If the queue is full, images sent in by Workers are discarded until there is space in the queue again. This means that a spammy job can starve the other jobs from queueing images.
It would be nice if there was not only a limit on the total number of queued images, but also a limit on the number of queued images per job. This per-job limit should be of the order of
G / J
, whereG
is the global limit, andJ
is the expected number of jobs to run in parallel.Changed status from 'Needs Triage' to: 'Confirmed'
Added subscriber: @dr.sybren