Cooperative scheduler #918
Conversation
From squash & rebase of branch aspectJ-experiment+coop-sched3+recreate-coop-scenario+alt-alt-gh802-reproducer at commit 334267e. Unit test classes omitted due to conflicts (TODO add to later PR): CONFLICT (content): Merge conflict in test/src/test/java/org/corfudb/runtime/concurrent/MapsAsMQsTest.java CONFLICT (content): Merge conflict in test/src/test/java/org/corfudb/runtime/collections/SMRMapEntrySetTest.java
|
Results automatically generated by CorfuDB Benchmark Framework to assess the performance of this pull request for commit 151fc94. *** 0.0% transaction FAILURE rate for NonConflictingTx+Scan workload, 1 threads, Disk mode An interactive dashboard with Pull Request Performance Metrics for ALL cluster types and numbers of threads in run, is available at: |
|
outdated and huge |
Introduce a cooperative-style scheduler for testing use. Test code using threads must opt into using the cooperative scheduler by explicitly registering themselves with the scheduler, removing themselves from the scheduler, etc. All code must be annotated with explicit calls to
CoopScheduler.sched(), similar toThread.yield()but with 100% deterministic/repeatable thread execution & interleaving.Deterministic coop thread scheduling is managed via a 'schedule', which is a list or array of thread numbers to execute in turn. In cases where the schedule is shorter than the total number of
sched()calls, the array is re-used ("wrap-around" style) to simulate a schedule of infinite length.