Hacker News Reader

Cgo overhead was made 5-30x faster in go1.21, and it was already within noise levels in this article, so i'd use that.

Can you provide a reference for that? A quick search for me didn't bring up anything. I'm curious to read more.

https://shane.ai/posts/cgo-performance-in-go1.21/

> Cgo calls take about 40ns, about the same time encoding/json takes to parse a single digit integer.

As an aside, that sure feels like a lot of time to parse a single-digit integer. Not catastrophic by any means, but still, 100 to 200 cycles is a sign the program is definitely Doing Something. Perhaps that’s the memory allocator?

It's probably just because it's using reflection which is pretty slow in general. Lots of conditions/branches and boxing/unboxing of values.

they changed the ABI in 1.17 to pass arguments in registers instead of the stack: https://go.dev/doc/go1.17#compiler so if you used this solution you might not need to do the fixup anymore if the ABI matches.

Doesn’t seem like there is. Probably because go developers want code to be pure go if possible