Open effectfully opened 1 week ago
/benchmark validation-decode
/benchmark validation-decode
/benchmark validation-decode
Click here to check the status of your benchmark.
Comparing benchmark results of 'validation-decode' on '1d9a758c1f' (base) and 'a803b77a84' (PR)
1d9a758 | a803b77 | Change | |
---|---|---|---|
TOTAL | 45.39 ms | 55.75 ms | +22.8% |
Click here to check the status of your benchmark.
Comparing benchmark results of 'validation-decode' on '1d9a758c1f' (base) and 'a803b77a84' (PR)
1d9a758 | a803b77 | Change | |
---|---|---|---|
TOTAL | 44.13 ms | 54.90 ms | +24.4% |
Click here to check the status of your benchmark.
Comparing benchmark results of 'validation-decode' on '1d9a758c1f' (base) and 'a803b77a84' (PR)
1d9a758 | a803b77 | Change | |
---|---|---|---|
TOTAL | 43.73 ms | 55.56 ms | +27.0% |
mkTermToEvaluate
is a part of the script preparation phase. It looks rather inefficient (in two different ways) and we don't seem to have any dedicated benchmarks for catching that other thanvalidation-full
, but that's too insensitive due to it evaluating the scripts. I really don't believe there's a good reason formkTermToEvaluate
to be inefficient, so I think we should include it in the decoding benchmarks.Let's see how much overhead
mkTermToEvaluate
contributes.