> 2. ultimately getting rid of cgo would probably help a lot anyway, cgo calls are pretty slow

It’s slow compared to a function call in C, but it’s still measured in nanoseconds. If you’re not calling C functions from a tight loop in Go it’s unlikely to be noticeable.