-
Notifications
You must be signed in to change notification settings - Fork 479
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Benchmark] Include 'mkTermToEvaluate' in 'benchmark-decode' #6667
base: master
Are you sure you want to change the base?
[Benchmark] Include 'mkTermToEvaluate' in 'benchmark-decode' #6667
Conversation
/benchmark validation-decode |
2 similar comments
/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) Results table
|
Click here to check the status of your benchmark. |
Comparing benchmark results of 'validation-decode' on '1d9a758c1f' (base) and 'a803b77a84' (PR) Results table
|
Click here to check the status of your benchmark. |
Comparing benchmark results of 'validation-decode' on '1d9a758c1f' (base) and 'a803b77a84' (PR) Results table
|
a803b77
to
074b5ce
Compare
/benchmark validation |
2 similar comments
/benchmark validation |
/benchmark validation |
Click here to check the status of your benchmark. |
Just checking that the benchmarking machine does not see no changes in performance as changes. |
Comparing benchmark results of 'validation' on '5eb80f3fe3' (base) and '074b5ce7b1' (PR) Results table
|
Click here to check the status of your benchmark. |
Comparing benchmark results of 'validation' on '5eb80f3fe3' (base) and '074b5ce7b1' (PR) Results table
|
Click here to check the status of your benchmark. |
Comparing benchmark results of 'validation' on '5eb80f3fe3' (base) and '074b5ce7b1' (PR) Results table
|
Damn, I don't like that we are not seeing pure noise here... |
/benchmark validation |
/benchmark validation |
3 similar comments
/benchmark validation |
/benchmark validation |
/benchmark validation |
Click here to check the status of your benchmark. |
Comparing benchmark results of 'validation' on '5eb80f3fe3' (base) and '074b5ce7b1' (PR) Results table
|
Click here to check the status of your benchmark. |
Comparing benchmark results of 'validation' on '5eb80f3fe3' (base) and '074b5ce7b1' (PR) Results table
|
Click here to check the status of your benchmark. |
Click here to check the status of your benchmark. |
Click here to check the status of your benchmark. |
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.