Is your feature request related to a problem? Please describe.

A clear and concise description of what the problem is - e.g. "I'm always frustrated when [...]"

The ability to trivially benchmark and examine regressions as they happen. Regressions currently can happen and they aren't caught. Luckily we've got folks like @harshavardhana and @klauspost who read through the code manually or noticed hot paths on their server, and will go fix problems like in #579 and #544, but unfortunately that change #579 didn't include benchmark results, though here are what they look like
https://dashboard.github.orijtech.com/benchmark/f746b02388744f02b238f582d1a87dfb

Describe the solution you'd like

What would the feature look like? How would it work? How would it change the API?

On the Github marketplace, you can add gobencher in 1-click per https://github.com/marketplace/gobencher and then you'll never have to worry about benchmarking, all commits will be benchmarked against the base branch automatically and reuslts presented to you, hassle free!

Describe alternatives you've considered

Are there alternatives you've tried, and/or workarounds in-place?

Manually benchmarking every change -- this is tedious, error prone and no one does this consistently in practice. We've detailed why and how we built bencher per https://medium.com/orijtech-developers/bencher-b60cc82e3ef1