Last-Rendered Image: refactor queue to be per job #99394

Open
opened 2022-07-04 14:36:32 +02:00 by Sybren A. Stüvel · 2 comments

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, where G is the global limit, and J is the expected number of jobs to run in parallel.

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`, where `G` is the global limit, and `J` is the expected number of jobs to run in parallel.
Author
Owner

Changed status from 'Needs Triage' to: 'Confirmed'

Changed status from 'Needs Triage' to: 'Confirmed'
Author
Owner

Added subscriber: @dr.sybren

Added subscriber: @dr.sybren
Sybren A. Stüvel added
Type
Design
and removed
Type
Report
labels 2023-02-17 11:17:23 +01:00
Sign in to join this conversation.
No Milestone
No Assignees
1 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: studio/flamenco#99394
No description provided.