Join GitHub today
GitHub is home to over 50 million developers working together to host and review code, manage projects, and build software together.
Sign upAdd benchmark code to tests #241
Open
Labels
Comments
drinckes
added a commit
that referenced
this issue
Nov 28, 2018
See #241 . Example output: BenchmarkEncode-2 2000000 950 ns/op 112 B/op 6 allocs/op BenchmarkDecode-2 2000000 859 ns/op 176 B/op 6 allocs/op The numbers are 1) the number of ops, 2) the time per op, 3) distinct memory allocations occurred per op, and 4) how many bytes were allocated per op. An encode took 950 nanoseconds, a decode 859 nanoseconds, so they are both a bit more than a million operations per second.
|
Go benchmarks added in #240 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
We should add benchmarking code to the tests so that performance impact of code changes can be identified.
Since the travis CI runs the tests on every pull, this should make performance testing of changes easy.