BUT -> +50% runtime in -O3 (+20ns) Investigation seems to indicate - that the increased (+1 Epochs, 10 -> 11) moving average caused the Algo to perform worse (strong effect) - that the Optimiser has problems with boost::rational, which however yields only a minute effect (+5ns), and only on the critical path The access via Meyers Singleton has no adverse effect, rather the new setup gives a tiny benefit (46ns -> 37ns). Surprisingly, the increased pre-allocation has no observable effect. |
||
|---|---|---|
| .. | ||
| 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 | ||