integrate Activity activation with Scheduler operation

[Ichthyostega]

As a Lumiera developer,
I need an integration of the Activity-Language with the Scheduler,
to be able to enqueue and dispatch render jobs.

further low-level implementation and integration work

The execution of »scheduler Activities« has been implemented against an abstracted environment. A set of dispatch operations has been specified at a logical level, allowing to define what comprises a correct execution of an Activity-chain. Now this task must be carried on by implementing these dispatch operations in terms of scheduler invocation and worker thread management.

Acceptance Criteria

Given

• a JobFunctor with suitable parameters (start time, deadline)
• a properly configured Scheduler instance in operational state

When

an activity::Term representing the Job is built

And

the entrance point to this term is instructed into the Scheduler

Then

the JobFunctor will be invoked, observing the defined timing constraints

[Ichthyostega]

After design and implementation of the WorkForce — which lead to a extended digression into library design, and a (#1279) re-assessment of thread support technology, the next step under the umbrella of the »Playback Vertical Slice« effort will be to follow up to the definition of »Render Activities« and the »Activity Language« (achieved with #1319) with the goal to establish the »Scheduler Service« as the actual implementation of »Render Activity« execution.

This ticket here addresses this integration work, and should lead to the demonstration of a running scheduler in a test setup.

• the first step should be low-level functionality at Scheduler-Layer-1
• the next step would be to provide the »Activity« execution at Scheduler-Layer-2
• and finally both should be combined into an integration test of the Scheduler Service

[Ichthyostega <prg@…>]

In 9ce3ad3/Lumiera:

Scheduler: Layer-2 complete and tested (see #1326)

• the implementation logic of the Scheduler is essentially complete now
• all functionality necessary for the worker-function has been demonstrated

As next step, the »Scheduler Service« can be assembled from the two
Implementation Layers, the Activity-Language and the BlockFlow allocator
This should then be verified by a multi-threaded integration test...

[Ichthyostega]

The »Scheduler Service« is complete and passes integration tests.
Processing of an extended load of interconnected jobs could be demonstrated.

The next goal is to conduct #1344 Performance- and Stress tests to weed out remaining issues and establish a baseline for the Scheduler's performance limits.

[Ichthyostega]

Through an extended series of stress tests #1344, using a test setup #1346 specifically developed for this purpose, some confidence was established that the new Scheduler implementation performs as expected within reasonable limits.

In the final integration test, extended operation over a time span of more than one minute could be demonstrated at full load and without significant overhead.

[Undercover Agent]

Migration MasterTickets ⟼ Subtickets-plugin