Ichthyostega
14a5200cc0
For comparison: use individual managment by refcount. This supports the conclusion that BlockFlow is more than just a custom allocator; it also supports a non-trivial lifetime management, and this comes at a cost. Playing around with various load patterns uncovers further weak spots in the regulation mechanism. As a remedy, introduce a stronger feed-back and especially set the target load factor from 100% -> 90% to add some headroom to absorb intermittent load peaks Presumably ''much more observation and fine-tuning'' will be necessary under real-world load conditions (⟹ Ticket #1318 for later) |
||
|---|---|---|
| .. | ||
| activity-detector-test.cpp | ||
| activity-detector.hpp | ||
| block-flow-test.cpp | ||
| scheduler-activity-test.cpp | ||
| scheduler-commutator-test.cpp | ||
| scheduler-invocation-test.cpp | ||
| scheduler-usage-test.cpp | ||