You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Dec 1, 2021. It is now read-only.
When working on another project lower level lib, I thought I'd like to look at the performance impact. I'm not too concerned, but I wanted some numbers to put behind me before I used it. I didn't find a benchmark in this repo so I wrote one:
package errors
import (
"fmt"
"testing"
"github.com/pkg/errors"
)
func noErrors(at, depth int) error {
if at >= depth {
return fmt.Errorf("no error")
}
return noErrors(at+1, depth)
}
func yesErrors(at, depth int) error {
if at >= depth {
return errors.Errorf("ye error")
}
return yesErrors(at+1, depth)
}
const stacks = 100
func BenchmarkNoErrors(b *testing.B) {
var err error
b.ReportAllocs()
for i := 0; i < b.N; i++ {
err = noErrors(0, stacks)
}
b.StopTimer()
b.Logf("%v", err)
}
func BenchmarkErrors(b *testing.B) {
var err error
b.ReportAllocs()
for i := 0; i < b.N; i++ {
err = yesErrors(0, stacks)
}
b.StopTimer()
b.Logf("%v", err)
}
It looks like the cost per op is roughly 1000-3000 ns. Which isn't a concern for me. But I'm glad to know it isn't more expensive.