Ichthyostega 097001d16f Scheduler: investigate timings of dispatch() ... ...there seemed to be an anomaly of 50...100µs ==> conclusion: this is due to the instrumentation code - it largely caused by the EventLog, which was never meant to be used in performance-critical code, and does hefty heap allocations and string processing. - moreover, there clearly is a cache-effect, adding a Factor 2 whenever some time passed since the last EventLog call ==> can be considered just an artifact of the test setup and will have no impact on the scheduler remark: this commit adds a lot of instrumentation code		2023-10-27 02:53:34 +02:00
..
activity-detector-test.cpp	Scheduler: access invocation time for test	2023-10-25 23:40:47 +02:00
activity-detector.hpp	Scheduler: investigate timings of dispatch()	2023-10-27 02:53:34 +02:00
block-flow-test.cpp	Library: switch Microbenchmark setup to C++17 threads	2023-09-24 18:07:28 +02:00
scheduler-activity-test.cpp	Scheduler: rectify λ-post API	2023-10-23 01:48:46 +02:00
scheduler-commutator-test.cpp	Scheduler: control structure for the worker-functor	2023-10-22 23:25:35 +02:00
scheduler-invocation-test.cpp	Scheduler: Layer-1 complete and tested	2023-10-17 04:35:58 +02:00
scheduler-load-control-test.cpp	Scheduler: setup to verify the work-Function	2023-10-25 17:31:32 +02:00
scheduler-service-test.cpp	Scheduler: investigate timings of dispatch()	2023-10-27 02:53:34 +02:00
scheduler-stress-test.cpp	Scheduler: plan for integration	2023-10-20 00:59:50 +02:00
scheduler-usage-test.cpp	Scheduler: plan for integration	2023-10-20 00:59:50 +02:00
work-force-test.cpp	Scheduler: rectify λ-post API	2023-10-23 01:48:46 +02:00