https://github.com/amscanne/golang-micro-benchmarks
Tiny collection of micro benchmarks.
https://github.com/amscanne/golang-micro-benchmarks
Last synced: 8 months ago
JSON representation
Tiny collection of micro benchmarks.
- Host: GitHub
- URL: https://github.com/amscanne/golang-micro-benchmarks
- Owner: amscanne
- Created: 2014-04-05T12:22:05.000Z (over 11 years ago)
- Default Branch: master
- Last Pushed: 2019-03-02T00:19:32.000Z (over 6 years ago)
- Last Synced: 2025-03-20T22:04:03.824Z (8 months ago)
- Language: Go
- Size: 8.79 KB
- Stars: 19
- Watchers: 3
- Forks: 1
- Open Issues: 0
-
Metadata Files:
- Readme: README.md
Awesome Lists containing this project
- awesome-go - golang-micro-benchmarks - Tiny collection of micro benchmarks. - ★ 15 (Benchmarks)
- awesome-go - golang-micro-benchmarks - Tiny collection of Go micro benchmarks. The intent is to compare some language features to others. (Benchmarks / Other Software)
- awesome-go-cn - golang-micro-benchmarks
- fucking-awesome-go - :octocat: golang-micro-benchmarks - Tiny collection of Go micro benchmarks. The intent is to compare some language features to others. :star: 5 :fork_and_knife: 0 (Benchmarks / Other Software)
- awesome-go - golang-micro-benchmarks - Tiny collection of Go micro benchmarks. The intent is to compare some language features to others. (Benchmarks / Other Software)
- awesome-go - golang-micro-benchmarks - | - | - | (Benchmarks / Other Software)
- awesome-go - golang-micro-benchmarks - Tiny collection of Go micro benchmarks. The intent is to compare some language features to others. - :arrow_down:0 - :star:5 (Benchmarks / Other Software)
- awesome-go-zh - golang-micro-benchmarks
README
Golang Benchmarks
=================
This is a tiny collection of micro benchmarks.
The intent is to compare some language feature to others.
The original benchmark arose from a simple question:
Suppose a runtime parameter is dynamic, but generically fixed.
* Is it best to build a new closure when it changes?
* Or simply evaluate the parameter in an if, continuously?
* Or should we write generic types, and use an interface?
Running
-------
To run the suite, use:
go test -bench=.