Add linear mutable array benchmarks #331
Merged
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.
Slightly more details on issue #328.
I only spent time on
reads
benchmark, which creates an arrayand iterates on it. On a recent GHC HEAD (
378c0bba7d
), here'rethe current results:
The benchmark methodology is not ideal, since all benchmarks include
creation of the underlying array/vector. The reason is that the
gauge
library we are using for benchmarks is not implemented with linear
arrows so we can not use its API easily to pass a linear value to a
benchmark. There might be a way to work around this implementation using
gauge
(or another benchmarking library), but I didn't spend too muchtime on it.