Ticket #466 (closed enhancement: fixed)

Opened 2 years ago

Last modified 19 months ago

Job queue priority

Reported by: MC-arjen Owned by: MC-arjen
Priority: major Milestone: MediaMosa 3.0
Component: Core Version:
Keywords: Cc:
MoSCoW: Should Have Estimated time after impact analysis:
Related to project: none Tested: no
Accepted: no Estimated Hours: 0

Description

Jobs are now handled by the fifo scheduling principle. All jobs (but especially the transcoding jobs) need the possibility to give a optional priority value, to give the job less priority. suggestion: nice parameter like in *nix.

Change History

Changed 2 years ago by Frans

  • moscow changed from Should Have to Must Have
  • milestone changed from MediaMosa X.X to MediaMosa 3.0

Changed 2 years ago by peter

  • moscow changed from Must Have to Should Have

Didn't make it to definitive set of must have issues for MM 3.0.

Changed 2 years ago by MC-arjen

  • proposed name: priority
  • range: -20 to 19
  • default: 0

all job start calls should implement this parameter. The job priority parameter must be used in de jobscheduler; lower (!) priority numbers have precedence. (rationale: similar to the unix nice and lp commands)

Changed 2 years ago by forgacs

  • owner set to MC-arjen
  • status changed from new to assigned

I have implemented the priority parameter for transcode, retranscode, analyse, still.
Range: -100 to 100.
Please, review it.

Changed 19 months ago by Frans

  • status changed from assigned to closed
  • resolution set to fixed
Note: See TracTickets for help on using tickets.