Algorithm state profiling
Added a method to the scheduler to return the number of algorithms in each state.
Useful for profiling multithreaded jobs where we see inefficient use of threads: are we limited by our CF/DF graph, by algorithm cardinality, or by some other locking mechanism?
Edited by Marco Clemencic