The "DIstributed Analytical BLOckchain" Benchmark Framework. (Diablo). Measures blockchains with a focus on real-world applications and workload generation.
Apache License 2.0
11
stars
8
forks
source link
[BUG] Secondary keeps collecting commit data after timeout #24
When the benchmark is done, it sequentially gets the results from all the secondaries, and (!) it synchronously waits for the results from each secondary in the same loop. It means that, the primary does not stop the secondary until it gets the result from the current secondary in the loop.
Here are the lengths of arrays with throughput windows from all the secondaries in one of the experiments with the duration of 120 seconds.
For the first secondary, we get pretty much the expected length — 123 windows of 1 second duration. But for all the subsequent secondaries, the number of windows increases. Therefore, the timeout value for the first secondary was 0 seconds, but for the last one, we see additional 27 second timeout.
When the benchmark is done, it sequentially gets the results from all the secondaries, and (!) it synchronously waits for the results from each secondary in the same loop. It means that, the primary does not stop the secondary until it gets the result from the current secondary in the loop.
Here are the lengths of arrays with throughput windows from all the secondaries in one of the experiments with the duration of 120 seconds.
[123, 126, 129, 131, 133, 134, 137, 141, 147, 147]
For the first secondary, we get pretty much the expected length — 123 windows of 1 second duration. But for all the subsequent secondaries, the number of windows increases. Therefore, the timeout value for the first secondary was 0 seconds, but for the last one, we see additional 27 second timeout.