Ecosyste.ms: Awesome
An open API service indexing awesome lists of open source software.
https://github.com/davecheney/autobench
Go benchmark harness.
https://github.com/davecheney/autobench
Last synced: about 1 month ago
JSON representation
Go benchmark harness.
- Host: GitHub
- URL: https://github.com/davecheney/autobench
- Owner: davecheney
- Created: 2013-03-28T11:17:01.000Z (over 11 years ago)
- Default Branch: master
- Last Pushed: 2014-07-28T04:52:21.000Z (over 10 years ago)
- Last Synced: 2024-11-09T02:22:10.566Z (about 1 month ago)
- Language: Go
- Homepage:
- Size: 1.01 MB
- Stars: 99
- Watchers: 10
- Forks: 29
- Open Issues: 2
-
Metadata Files:
- Readme: README.md
Awesome Lists containing this project
- awesome-go - autobench - Go benchmark harness. - ★ 88 (Benchmarks)
- awesome-go-extra - autobench - 03-28T11:17:01Z|2014-07-28T04:52:21Z| (Benchmarks / Other Software)
README
autobench
=========`autobench` is a framework to compare the performance of Go 1.2 and Go 1.3.
usage
-----`autobench` downloads and builds the latest Go 1.1 and Go tip branches and runs a set of Go 1 benchmarks for comparison.
Useful targets are
make bench # runs all benchmarks, _once_
make go1 # runs bench/go1 benchmarks _once_
make runtime # runs bench/runtime benchmarks _once_
make http # runs bench/http benchmarks _once_
make float # runs bench/float benchmarks _once_
make extra # runs extra benchmarks.
make clean # removes any previous benchmark results
make update # updates both branches to the latest revision, clears any benchmark resultsYou can optionally benchmark with gccgo instead of gc by either uncommenting the corresponding line in the Makefile or by setting TESTFLAGS to an appropriate value:
make TESTFLAGS=-compiler=gccgo bench
known issues
------------* If you are benchmarking on Freebsd, you may need to use `gmake`.
contributing
------------Contributions and pull requests are always welcome. If you are submitting a pull request with benchmark data, please include the value of OLD and NEW at the top of the Makefile in the suffix of your file (follow the examples) so we can trace which revision this benchmark was taken from. If you want to include commentry in your benchmark, comments should start with a #.
make > linux-386-go1.2.1-vs-go.1.3beta1.txt
licence
-------This package uses benchmark code from the Go project. Where otherwise unspecified this code is released into the public domain.