This proposes to increase the --filter-short threshold from 0.6 to 1.0 seconds. The reason is that the LLVM test-suite is quite noisy and this is one mitigation for that. I.e., if we filter out all apps with a runtime of less than a second, then the variation between runs is a lot less and we get less noisy results. I appreciate this replaces one arbitrary number with another arbitray number, but a runtime of at least 1 second for a benchmark seemed reasonable to me.
As a result, less results/benchmarks will be reported. On the system that I tested it, this means that for the MultiSource benchmarks the following apps will be excluded in addition to the ones that already got excluded with --filter-short:
Program exec_time Benchmarks/DOE-ProxyApps-C/CoMD/CoMD 0.92 Benchmarks...VC/Expansion-flt/Expansion-flt 0.84 Applications/viterbi/viterbi 0.78 Benchmarks...ataFlow-flt/GlobalDataFlow-flt 0.76 Benchmarks/Trimaran/enc-rc4/enc-rc4 0.74 Benchmarks/BitBench/five11/five11 0.97 Benchmarks/Prolangs-C++/life/life 0.65 Benchmarks...VC/Symbolics-flt/Symbolics-flt 0.73 Benchmarks...Fhourstones-3.1/fhourstones3.1 0.69 Benchmarks/VersaBench/dbms/dbms 0.85 Benchmarks.../DOE-ProxyApps-C++/CLAMR/CLAMR 0.81 Benchmarks...roxyApps-C/SimpleMOC/SimpleMOC 0.88 Benchmarks...alencing-dbl/Equivalencing-dbl 0.63 Benchmarks/nbench/nbench 0.89 Benchmarks/ASCI_Purple/SMG2000/smg2000 0.94 Benchmarks...aran/netbench-crc/netbench-crc 0.66
what happens to filter_short_threshold on exception? Is it a stable behaviour?