Fix benchmark interval count jitter
As the benchmark policy and the interval statistics start at nearly exactly the same time this could cause the interval statistics to report one interval too much or not. This change slightly delays to policy start and suppresses printing of the last incomplete interval. That way the first interval captures slightly too little data (but that doesn't matter as it's normally cut off anyways) and the last incomplete interval only captures data for the fraction of a second.
Loading
Please register or sign in to comment