cmd/benchstat: new version of benchstat Remember that if you're doing benchmarking, use benchstat instead of benchcmp. #golang go-review.googlesource.com/c/perf/+/30996…

Here's a list of some changes to look forward to in #golang 1.18! The first beta should be out in a month, and the final release in three months. Each change with a link, so you can read more.

The compiler currently compiles a+b+c+d as a+(b+(c+d)). It should use (a+b)+(c+d) instead, because the latter can be executed out of order. More broadly, we should balance trees of associative comp...

I run this bot to collect benchmarks; anyone who's watching Go-1.18 release, we (MK) shrank the starting heap size, which is superficially good, but lots of small benchmarks ran entirely within the old initial heap and now they don't -- our metrics went kerflooie.…

Google's Go compiler and runtime team meets periodically (roughly weekly) to discuss ongoing development of the compiler and runtime. While not open to the public, there's been desire by th...

Using go devel +ed4a27a Currently, functions with for-loops are not inline-able, would be nice if they did. Not long ago, I used a non-idiomatic goto in order to cheat around the inliner. @dr2chase

$ go version go version devel go1.17-dc00dc6c6b Thu Jun 10 12:41:37 2021 +0000 linux/amd64 Issue #38184 seems to be a reasonably hard limit in the race detector library, but it's not always...

What version of Go are you using (go version)? $ go version go version go1.18beta1 windows/amd64 Does this issue reproduce with the latest release? It reproduces on the 1.18 Beta 1 release. What op...

The sha_ni sha256 instructions have been shown to provide an ~4x increase in hash rate on newer amd64 systems versus the avx2 implementation. Transliterating the Linux implementation shows an up to...

The generated x86 code can be improved in some fairly simple ways - hoisting computed constants out of loop bodies, and avoiding unnecessary register moves - that have a significant performance imp...

What is your favorite #golang code micro-optimization that is effective, but not very intuitive and can easily be missed out? We know that slice preallocation and things like that are important. But that's mainstream. :) I wonder what little tricks do you…

Pixie Blog

How I sped up GoAWK by switching from a tree-walking interpreter to a bytecode compiler and virtual machine interpreter.

Shows how much the performance of Go has improved from version 1.2 through to 1.18 -- in its compiler, runtime, and libraries.

Contribute to felixge/benchmore development by creating an account on GitHub.

Languages Regex Benchmark: Language Email(ms) URI(ms) IP(ms) Total(ms) C PCRE2 25.00 25.02 5.65 55.66 Rust 31.31 31.73 6.75 69.79 PHP 54.39 50.22 5.80 110.40 Javascript 74.88 63.09 2.02 140.00 D ld...