Introducing a fixed pre-delay on each new Calc-Streem seemed like an obvious remedy, yet on closer investigation it turned out that the start-up logic as such was contradictory, which was only uncovered by some rather special schedule patterns. After fixing the logic deficiencies, Scheduler starts up as intended and the probabilistic capacity-control seems to work as designed. Thus no need to introduce an artificial delay at begin, even while this implies that typically the first round of job-planning will be performed synchronous, in the invoking thread (which may be surprising, but is completely within the limits of the architecture; we do not employ specifically configured threads and planning should be done in short chunks, thus the first chunk can well be done by the caller) |
||
|---|---|---|
| .. | ||
| draw | ||
| DIR_INFO | ||
| empty.html | ||
| InterfaceConcept_Varga.mm | ||
| renderengine.html | ||
| thinkPad.ichthyo.mm | ||
| uml | ||
| workflow.mm | ||