Add more microbenchmarks to assess interpreter performance #121
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
First this PR reorganizes the benchmarks introduced in #119 and renames them.
Benchmarks now try to consistently use a name that roughly describes the expression that is evaluated in the loop body.
Each benchmark follows the same structure that tries to focus the execution of a particular expression. It is executed 30 times inside a loop, which hopefully should make sure that these expressions dominate the overall execution time.
The current micro, or perhaps rather nanobenchmark set is:
arg
arr at: 1
arr at: 1 put: 2
[ 0 ] value
42
field := 1
field
field := field + 1
field := field
GlobalRead
local := 1
local
local := local + 1
local := local
self trivial
trivial = ( ^ 1 )
self trivial
trivial = ( [ ^ 42 ] value )
Core-Lib Updates