Joshua Boniface
252175fb6f
1. Move to a time-based (60s) benchmark to avoid these taking an absurd amount of time to show the same information. 2. Eliminate the 256k random benchmarks, since they don't really add anything. 3. Add in a 4k single-queue benchmark as this might provide valuable insight into latency. 4. Adjust the output to reflect the above changes. While this does change the benchmarking, this should not invalidate any existing benchmarks since most of the test suit is unchanged (especially the most important 4M sequential and 4K random tests). It simply removes an unused entry and adds a more helpful one. The time-based change should not significantly affect the results either, just reduces the total runtime for long-tests and increase the runtime for quick tests to provide a better picture. |
||
|---|---|---|
| .. | ||
| pvc | ||
| scripts | ||
| setup.py | ||