and the conclusion is.
Encoding got a decent bit faster.
whilst, decoding got noticeably slower.
earlier on i had already found conversion to int16 was a lot slower than
int32, so I’d was already up.
/* Hal3 Sun Jun 19 00:53:10 BST 2016 go version go1.7beta2 linux/amd64
BenchmarkPCM8b
OK got it, i wasn't using a package level var to store the result.
--
You received this message because you are subscribed to the Google Groups
"golang-nuts" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to golang-nuts+unsubscr...@googlegroups.com.
For m
thanks,
i was guessing something like that, these are very short pieces of linear
code.
so i did try; using returned values, repeating the test 10x in the loop,
and adding stop/start.
the code's on github, (https://github.com/splace/signals) but this is a
selective test, so its really buried,
Without seeing the code (hint, hint) I'm guessing that your benchmark got
optimised away.
Here are some links with suggestions on how to make your benchmark reliable.
http://dave.cheney.net/2013/06/30/how-to-write-benchmarks-in-go#compiler-optimisation
http://talks.godoc.org/github.com/davechene
