benchmarking machinery - #515
Open
Rewbert wants to merge 1 commit into
Open
Conversation
Merged
Owner
|
hlint fails |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
A proposal for some simple benchmarking machinery, to track how changes to the compiler or runtime affect the runtime behavior of MicroHs. I asked a Clanker for the code that parses the
+RTS -v -RTSoutput.If you issue
make bench, it will build the sample benchmark programs included here, and then execute them. It will run each five times (override-able) to gather multiple GC times and execution times. The reduction count, allocation counts, etc, all appear to be deterministic, and are gathered only once. The result is written to a JSON file, named via the current Unix timestamp.The idea is perhaps that some software yet to be written can read the JSON and render is nicely or something, but I have not written such a software. I've proposed some initial sample benchmarks, intended to exercise different things, but this is by no means exhaustive.
This is a proposal, and I am happy to hear what you think.