LUMIERA.clone/tests/vault/gear
Ichthyostega 049ca833a0 Block-Flow: optimise parameters for performance
There seems to be a ''sweet spot'' for somewhat larger Epoch sizes around 500 slots.
At least in the test setup used here, which works with a load of 200 Frames / sec,
which is significantly over the typical value of 50fps (video + audio) for simple playback.

The optimisation of averaged allocation times can not be much improved **below 30ns**.

Overall, this can be considered a good result,
since this allocation scheme does way more than just allocate memory,
it also provides a means to track dependencies and lifecycle.

__For context__:
 - we should strive at processing one frame in ~ 10ms
 - for 10 Activity records per Frame, we currently use < 0.5 µs for
   memory and dependency management in the scheduler
 - this leaves enough room for the further administrative efforts
   (priority queue, job planning, buffer management)
2023-07-21 04:34:04 +02:00
..
activity-detector-test.cpp Block-Flow: define next steps to construct 2023-07-13 01:51:21 +02:00
activity-detector.hpp Block-Flow: define next steps to construct 2023-07-13 01:51:21 +02:00
block-flow-test.cpp Block-Flow: optimise parameters for performance 2023-07-21 04:34:04 +02:00
scheduler-activity-test.cpp Block-Flow: define next steps to construct 2023-07-13 01:51:21 +02:00
scheduler-commutator-test.cpp Scheduler: investigate modes of operation 2023-07-03 18:40:37 +02:00
scheduler-invocation-test.cpp Scheduler: investigate modes of operation 2023-07-03 18:40:37 +02:00
scheduler-usage-test.cpp Scheduler: investigate modes of operation 2023-07-03 18:40:37 +02:00