runners: Adopted cumulative results in bench probes
Now that csv.py's accumulate/delta functions make it easy to switch between delta/cumulative results, we might as well make the default results consistent. The previous difference between n/bench_runtime vs bench_readed/ bench_simtime risked a lot of confusion. Note we can't use delta results for n, as it doubles as a unique index for each probe measurement. If we want consistency the only option is cumulative results. At least that makes the decision easy.
This commit is contained in:
@@ -584,7 +584,7 @@ benchmarks: $(BENCH_CSV)
|
||||
-bprobe='%(case)s+%(probe)s' \
|
||||
-Fi='min(enumerate())' \
|
||||
-fn='max(n)' \
|
||||
-ft='float(bench_simtime)/1.0e9' \
|
||||
-ft='max(float(bench_simtime)/1.0e9)' \
|
||||
-o-) \
|
||||
-bprobe \
|
||||
-fn \
|
||||
@@ -604,13 +604,13 @@ benchmarks-diff: $(BENCH_CSV)
|
||||
-bprobe='%(case)s+%(probe)s' \
|
||||
-Fi='min(enumerate())' \
|
||||
-fn='max(n)' \
|
||||
-ft='float(bench_simtime)/1.0e9' \
|
||||
-ft='max(float(bench_simtime)/1.0e9)' \
|
||||
-o-) \
|
||||
-d <(./scripts/csv.py $(BUILDDIR)/lfs3.bench.csv \
|
||||
-bprobe='%(case)s+%(probe)s' \
|
||||
-Fi='min(enumerate())' \
|
||||
-fn='max(n)' \
|
||||
-ft='float(bench_simtime)/1.0e9' \
|
||||
-ft='max(float(bench_simtime)/1.0e9)' \
|
||||
-o-) \
|
||||
-bprobe \
|
||||
-fthroughput='avg(float(n) / max(t, 1.0e-9))' \
|
||||
@@ -625,7 +625,7 @@ benchmarks-bottlenecks: $(BENCH_CSV)
|
||||
-bprobe='%(case)s+%(probe)s' \
|
||||
-Fi='min(enumerate())' \
|
||||
-fn='max(n)' \
|
||||
-ft='float(bench_simtime)/1.0e9' \
|
||||
-ft='max(float(bench_simtime)/1.0e9)' \
|
||||
-fruntime='max(bench_runtime)' \
|
||||
-o-) \
|
||||
-bprobe \
|
||||
|
||||
Reference in New Issue
Block a user