Looper validation and back pressure detection #4
Description
The looper right now is not validated. We need to validate its behaviors when under back pressure: does it correctly collapse into a busy loop under back pressure? Does it correctly go back to the normal batching/discretization behavior after it comes back from back pressure?
Further, the looper emits the OuterLoopStats, but this information is not recorded nor used. I suspect we can log it into SQLite for analysis as well. We should also export more data here, like the amount of time it spent in "saturation"/busy-loop vs the amt of time it spent during batch operations. This analysis may be useful for post processing the benchmark result